Skip to main content
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.
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

1

Start a new workspace

From the workspaces area or your dashboard, choose New workspace.
2

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).
3

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.
4

Save

Save the workspace. You are taken to its settings, where you can adjust taxonomies and option filters.
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.

​
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.
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.
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.
  • 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.
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.

​
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.
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.
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.

​
Cloning a workspace

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

Open the workspace settings

Go to the workspace you want to copy and open its settings.
2

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”.
3

Confirm

Confirm. Terminus Hub creates the new workspace and opens it.
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.

​
Deleting a workspace

Open the workspace’s settings and choose to delete it, then confirm. Deletion cannot be undone.
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.

​
When to use multiple workspaces

Per team

Give each team its own workspace so submissions and records stay separate and members see only what is relevant.

Per region

Run separate efforts for different markets, sharing the same taxonomy definitions.

Per environment

Keep a live workspace and a staging workspace to try taxonomy changes before rolling them out.
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.

Workspaces reference

The full workspace concept, scoping, and settings.

Team members

Invite people and assign workspace access and roles.

Filter options per taxonomy

Limit which dropdown options appear in a workspace.

Review and approve submissions

What the require-review setting changes.