## What a workspace is

Every collection belongs to exactly one **workspace**. Access to a private collection is governed by who is a member of its workspace and what role they hold. Use separate workspaces per team or project to keep collections and people cleanly scoped.

Switch between your workspaces with the **workspace switcher** dropdown in the top bar. Create new ones from there or from your [account page](/content/docs/account-and-api-keys/index.html).

The workspace switcher — workspaces grouped by organisation, with quick links to create or manage them.

## Members and roles

Open **Workspace settings → Members** to manage who’s in:

- **Owner** — full control, including deleting the workspace.
- **Admin** — manage members and collections.
- **Member** — work with collections per their grants.

Admins can **invite** new members by email.

## Accepting an invitation

When you’re invited, you get an email with a link. Opening it lands you on an **accept** page:

1. **Sign in** (or create an account) with the invited email address.
2. **Accept** the invitation — you’re added to the workspace (or organisation) with the role the inviter chose.
3. You’re dropped into the workspace, and it appears in your [workspace switcher](/content/docs/workspaces/#what-a-workspace-is/index.html) from then on.

Organisation invites work the same way and can carry workspace grants, so accepting one can join you to the org _and_ the right workspaces at once. See [Organisations](/content/docs/organisations/index.html). Roles you might be granted are summarized in [Roles & permissions](/content/docs/roles-and-permissions/index.html).

## Trash

Deleting a collection doesn’t destroy it immediately — it moves to the workspace **Trash** tab, where you can **restore** it or **permanently delete** it within the retention window. This is the recovery path if a collection is removed by mistake (deletion is initiated from a collection’s **Actions** tab — see [Collection settings](/content/docs/collection-settings/index.html)).

## General

The **General** tab shows the workspace name, created date, its state (active / archived), and the organisation it belongs to (if any).

## Workspaces under an organisation

A workspace can sit under an **organisation**, which adds a layer of centralized membership and billing above individual workspaces. Org membership and workspace membership stay distinct — being in the org doesn’t by itself grant access to a workspace’s collections. See [Organisations](/content/docs/organisations/index.html).