Getting StartedAccount & Billing

Create a workspace

View as Markdown

A workspace is a space inside your organisation for a project, a team, or an environment. API keys live in a workspace and usage is attributed to it, while billing stays at the organisation level — so every workspace draws from the same credit balance and appears on the same bill.

This is the right tool for almost every “we need to separate things” case: separate dev from prod, separate one product from another, or give one team access to their project only.

Only an organisation Owner can create a workspace. If you are a Member, the Add Workspace button is not available to you — ask an Owner.

Steps

1

Open workspace settings

Go to Settings → Organisation → Workspaces. The table lists every workspace you have access to, with who created it, which products it uses, and when it was created.

2

Click Add Workspace

The button is at the top right of the page.

You can also reach this from the organisation switcher at the top of the sidebar: Add Workspace or Organisation → Add workspace.

3

Confirm the organisation

Current Organisation is shown but not editable — the workspace is created in whichever organisation you are currently in. To create a workspace somewhere else, switch to that organisation first.

4

Name it and create

Enter a Workspace Name — for example Production, Staging, or a project name — then click Add Workspace.

After creating it

1

Create an API key in it

Open API Keys with the new workspace selected and create a key. Calls made with that key are attributed to that workspace.

2

Give people access

Workspace access is granted per person. Either invite someone new and select this workspace during the invite, or edit an existing member and add the workspace to them. See Invite your team.

You do not need to add credits — the workspace uses the organisation’s existing balance immediately.

Workspace settings

Switch the settings scope from Organisation to Workspace to manage a single workspace. There are two pages:

  • General — workspace name, workspace ID, your role in this workspace, whether it is the default workspace, member count, and which products it uses.
  • Members — who can access this workspace and their workspace role.

Editing a workspace requires Admin on that workspace. Organisation Owners are Admin on every workspace automatically.

Naming conventions that work well

Production, Staging, Development. The most common setup, and the one that gives you the biggest safety win: revoking a staging key never touches production traffic.

Voice Assistant, Call Analytics, Docs Pipeline. Use this when you want per-product usage attribution on one bill.

Growth, Platform, Research. Use this when access control matters more than usage reporting.

You can create up to 100 workspaces per organisation. Deleted workspaces do not count towards the limit.