> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/workspaces/create-and-switch-workspaces.md).

# Create and switch workspaces

Workspace identity should be obvious before a user changes data, access, ontology, workflow, model, or release state. The sidebar workspace control switches the complete operating boundary; New Workspace starts a separate onboarding flow.

### Before you make the change

* Define why the new boundary cannot be represented by a project inside an existing workspace.
* Name accountable owners, identity policy, data policy, environment, and capacity owner.
* Choose a name that distinguishes the organization or program without exposing sensitive details.

### Follow the interface

#### Open the workspace switcher

![Workspace switcher in the Unitlab sidebar](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2F4jGdNCVAjx3AXBzWerLu%2Fworkspace-switcher.png?alt=media\&token=3874b3f5-b671-44c8-aefe-4851e9d06723)

*Choose the active workspace name at the bottom of the sidebar. Select another workspace to switch context, or choose New Workspace to begin creation.*

Switching changes the workspace-scoped projects, Data Space, datasets, ontologies, models, releases, members, roles, API keys, cloud storage, billing, and settings visible to the user.

#### Create the new workspace boundary

![Create your workspace screen with workspace name and Personal or Team usage](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FgFlTnhlxK6re6ODNlD4T%2Fworkspace-create.png?alt=media\&token=42d2589d-5acb-40af-a60a-150679258efc)

*Enter the Workspace Name, choose Personal or Team usage, then continue through the current onboarding flow. Usage describes the intended operating context; it does not replace role and permission design.*

### Understand the product behavior

1. The user authenticates.
2. If no workspace exists, Unitlab opens the workspace wizard.
3. The user selects a purpose: Work, Education, or Personal.
4. The user enters a workspace name.
5. The user can optionally invite teammates.
6. Unitlab creates the workspace, makes the user Owner, provisions the free subscription, and creates the initial workspace API key.
7. The application switches into the new workspace and guides the user toward projects.

Guided quick-start actions include creating a project, creating or cloning a release, inviting members, integrating a model, configuring reviewer or custom-model projects, trying batch/crop auto-annotation or Magic Touch, and opening project/member statistics.

### Create and enter a workspace

{% stepper %}
{% step %}

#### 1. Open the switcher

Choose the active workspace name in the lower-left sidebar.
{% endstep %}

{% step %}

#### 2. Choose New Workspace

Use the dedicated action at the end of the workspace list; do not create a workspace for a temporary task that belongs in a project.
{% endstep %}

{% step %}

#### 3. Name the boundary

Enter the durable organization, environment, or program name.
{% endstep %}

{% step %}

#### 4. Choose usage

Select Personal for an individual operating boundary or Team for a team or organization context, then choose Continue.
{% endstep %}

{% step %}

#### 5. Complete onboarding

Confirm the purpose and enter the new workspace before adding shared data or inviting members.
{% endstep %}

{% step %}

#### 6. Establish ownership and controls

Add accountable owners, configure roles, enable personal 2FA, and define API-key and cloud-connection ownership.
{% endstep %}

{% step %}

#### 7. Switch safely

When returning through the switcher, verify the workspace name and relevant item count before any privileged or bulk action.
{% endstep %}
{% endstepper %}

### Decisions that affect production

| Decision             | Production guidance                                                                                                                              |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Workspace vs project | Use a new workspace for a durable identity, ownership, policy, billing, or data-isolation boundary; use a project for work inside that boundary. |
| Personal vs Team     | Choose the operating context that matches ownership; team access still requires explicit member and role configuration.                          |
| Owners               | Use more than one accountable owner where policy permits to avoid recovery dependence on one person.                                             |
| Automation           | Bind jobs to explicit workspace and resource IDs, never to whichever workspace a human last opened.                                              |

### Continue the operating flow

* Invite approved members and assign minimum roles.
* Configure cloud storage and API keys only after ownership is recorded.
* Create the first project inside the verified workspace.