# Getting started

This page is for a team deciding how to begin with Volobox: how to get a workspace, and the first few things to do in it. It is a high-level path, not a checklist you must finish. Volobox is usable from the first sign-in.

## From a demo to your own workspace

Every start begins with a [free demo](/demo), where we show Volobox on work like yours and answer your questions. After the demo we set up your own cloud workspace the same day, and you get a 30-day free trial of it.

The trial is your real workspace: the projects, docs and agents you set up in it are your own. When it ends, you choose a plan or the workspace is closed. See [Pricing](/pricing) for plans.

> **Note:** Private cloud and on-premise deployments start with a conversation rather than a trial.

## The administrator's setup checklist

Administrators get a **setup checklist** with the recommended and optional steps for a new workspace: models, sandboxes, code hosts, teammates and more.

Each step is read from the live configuration. A step that is already done shows as done, and one that breaks later opens again by itself. Nothing on it is mandatory: an administrator can skip a step with a note for the rest of the admin team.

## Invite your people

An administrator adds the team, one person at a time or by importing a list of email addresses. Groups bundle people for chat, project membership and Docs and file sharing, so access is given once per group.

People from other companies, such as customers and external collaborators, are invited separately. They reach only the Portal, never the workspace itself (see [Support](/docs/support)).

## Create a first project

A project holds tasks, requests and the project's own chat channel. When you create one you choose:

- its name
- whether it is **public**, which means visible to every workspace member and never to the internet
- which task fields it uses
- whether coding is on

Then add members with a role. Starting with one project and one team is the usual way in: you do not have to move everything at once.

![The Fieldwork project open on its Delivery board: To do, In progress, In review and Done columns of task cards with type, priority, effort and label chips, assignee initials, and two cards assigned to the Software Developer agent.](https://volobox.io/docs/images/projects-board.light.webp)

*A project on its Tasks tab as a board: task cards in To do, In progress, In review and Done, some assigned to a team agent.*

## Connect a repository

For software work, an administrator connects the code host (GitHub, GitLab.com or Azure DevOps) and registers the organization's repositories. A project then links the repositories it works on. After that, people and agents start coding sessions from tasks, and the project shows its pull requests, branches and previews.

GitHub and GitLab repository links can also mirror issues as requests or tasks, so a team can keep using its issue tracker while it tries Volobox.

The guides walk through each code host: [Connect GitHub](/docs/connect-github), [Connect GitLab](/docs/connect-gitlab) and [Connect Azure DevOps](/docs/connect-azure-devops).

## Meet your personal assistant

Every person gets a **personal assistant** the moment their account exists. It is private to them. It answers how Volobox works, searches the team's docs and work, and in **Agent mode** proposes changes on approval cards that run only when they approve, unless a standing rule they set covers it.

Shared team agents are added by administrators. **Volly**, a built-in shared agent, can be mentioned in any team chat from day one.

Library packs add ready-made agents, skills and commands when an administrator chooses to install them. Nothing is installed automatically.

## Related

- [Introduction](/docs/introduction)
- [Workspace](/docs/workspace)
- [Projects](/docs/projects)
- [Agents](/docs/agents)
- [Integrations](/docs/integrations)
- [Request a demo](/demo)
