> ## Documentation Index
> Fetch the complete documentation index at: https://docs.terminus.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Workspaces in Terminus Hub

> Create workspaces, connect taxonomies, assign members, clone, and delete them from the account.

<Info>
  A workspace is a named area inside your account where work happens: it connects one or more taxonomies and holds the submissions and records made against them. Use workspaces to split work by team, brand, region, or client while sharing the same account-level taxonomy definitions. This page covers managing workspaces from the account. For the full concept, see the [workspaces reference](/reference/workspaces).
</Info>

Every account starts with one workspace named **Main**. It is an ordinary workspace: you can rename, clone, or delete it like any other. Only account owners and admins can create, clone, or delete workspaces.

## Creating a workspace

<Steps>
  <Step title="Start a new workspace">
    From the workspaces area or your dashboard, choose **New workspace**.
  </Step>

  <Step title="Name it">
    Give it a clear name. The name must be unique within the account and appears in the sidebar and member-facing views, so make the purpose obvious (for example, `EMEA Sales` or `Staging`).
  </Step>

  <Step title="Connect taxonomies">
    Assign the taxonomies this workspace should collect submissions for. A workspace with no taxonomies cannot collect anything, and Terminus Hub flags it until you add at least one.
  </Step>

  <Step title="Save">
    Save the workspace. You are taken to its settings, where you can adjust taxonomies and option filters.
  </Step>
</Steps>

<Note>
  On some plans the number of workspaces is capped. If you reach the limit, creating another is blocked and Terminus Hub shows a prompt to upgrade.
</Note>

## Connecting taxonomies

A workspace can only collect submissions for the taxonomies it is connected to. In a workspace's settings, pick the taxonomies it should use.

<Warning>
  The taxonomy list is replaced on each save, not merged. Send the complete set you want: any taxonomy you leave out is disconnected, along with its per-workspace option filters. Saving with none connected disconnects them all.
</Warning>

Each connected taxonomy also carries two per-workspace controls:

* **Option filters.** Limit which dropdown options that taxonomy shows in this workspace, as an allowlist (`include`) or a blocklist (`exclude`). This lets one taxonomy show a different subset of options per workspace. See [filter options per taxonomy](/recipes/filter-options-per-taxonomy).
* **Require review.** Make submissions for that taxonomy in this workspace go through approval before they become records. Turning review on may require a plan that includes approval workflows; turning it off is always allowed. See [review and approve submissions](/guides/review-and-approve-submissions).

A taxonomy comes from a published revision of its governance model. If a taxonomy has no published revision yet, publish it before collecting submissions. See [publish a revision](/guides/publish-revision).

## Assigning members to a workspace

Account owners and admins can reach every workspace automatically, so you never assign them. Only people whose account role is **Member** need explicit workspace access.

<Note>
  You assign workspace access from the account's people pages, not from the workspace itself. Open **Admin > Members**, invite or edit a member, and use the workspace picker to choose which workspaces they can reach and their role in each.
</Note>

Each assignment carries a workspace role: **Admin** (manage the workspace), **Member** (create and edit submissions), or **Viewer** (read-only). For the full flow, see [Team members](/account/team-members).

## Cloning a workspace

Cloning copies a workspace's configuration into a new one in the same account, so you do not repeat setup.

<Steps>
  <Step title="Open the workspace settings">
    Go to the workspace you want to copy and open its settings.
  </Step>

  <Step title="Clone it">
    Choose **Clone the workspace** and give the copy a name. The name must be unique in the account; a clash is rejected. The default suggestion is the original name followed by "Copy".
  </Step>

  <Step title="Confirm">
    Confirm. Terminus Hub creates the new workspace and opens it.
  </Step>
</Steps>

<Warning>
  Cloning copies only the configuration: the connected taxonomies and their per-workspace option filters. Members, submissions, and records are not copied, so you assign members to the clone separately. Whether the require-review setting carries over is not guaranteed, so re-check review on the clone.
</Warning>

## Deleting a workspace

Open the workspace's settings and choose to delete it, then confirm. Deletion cannot be undone.

<Warning>
  A workspace that still owns submissions, records, or members may refuse to delete and show an error. Move or clear that content first, or delete an empty workspace. Before deleting anything that holds data, export what you need: it cannot be recovered.
</Warning>

## When to use multiple workspaces

<CardGroup cols={3}>
  <Card title="Per team" icon="users">
    Give each team its own workspace so submissions and records stay separate and members see only what is relevant.
  </Card>

  <Card title="Per region" icon="globe">
    Run separate efforts for different markets, sharing the same taxonomy definitions.
  </Card>

  <Card title="Per environment" icon="layer-group">
    Keep a live workspace and a staging workspace to try taxonomy changes before rolling them out.
  </Card>
</CardGroup>

Workspaces share the account's taxonomy definitions, but each workspace's submissions and records belong to it alone. Members see only the workspaces they are assigned to.

## Gotchas

* **Main is not special.** The seeded "Main" workspace behaves like any other and can be renamed or deleted.
* **Taxonomies are replaced, not patched.** Saving the taxonomy list sends the full set; anything omitted is disconnected along with its option filters.
* **No taxonomies, no submissions.** A workspace must have at least one taxonomy connected before it can collect anything.
* **Members are assigned from the account, not the workspace.** Use the member's record under **Admin > Members** to grant workspace access.
* **Clone copies config only.** Members, submissions, and records are left behind, and require-review may not carry over.
* **Delete can be blocked.** A workspace holding records, submissions, or members may not delete until that content is gone.

## Related

<CardGroup cols={2}>
  <Card title="Workspaces reference" icon="book" href="/reference/workspaces">
    The full workspace concept, scoping, and settings.
  </Card>

  <Card title="Team members" icon="users" href="/account/team-members">
    Invite people and assign workspace access and roles.
  </Card>

  <Card title="Filter options per taxonomy" icon="filter" href="/recipes/filter-options-per-taxonomy">
    Limit which dropdown options appear in a workspace.
  </Card>

  <Card title="Review and approve submissions" icon="check" href="/guides/review-and-approve-submissions">
    What the require-review setting changes.
  </Card>
</CardGroup>