Skip to content
TriedDocs
Account and security

Workspaces

Create, switch, rename, transfer, leave and delete workspaces, and what each workspace owns.

A workspace is the unit of tenancy in Tried. Agents, LLMs, flows, knowledge bases, phone numbers, calls, chats, contacts, API keys, webhooks, billing and settings all belong to exactly one workspace. One user can belong to several workspaces and switch between them from the sidebar.

Every row in the database carries a workspace_id, and every query is scoped to the workspace of the signed-in session or the API key. The API never accepts a workspace_id from the request body, so a key for one workspace cannot read or change another workspace's data. Requests for an ID in another workspace return 404.

What a workspace contains#

Area Examples
Build Agents and their versions, Retell LLMs, conversation flows, knowledge bases, voices, tests
Deploy Phone numbers, SIP trunks, batch calls, public keys for widgets
Data Calls, chats, contacts, recordings, exports
System Members and invites, API keys, webhook URL, billing and credit, limits, reliability settings, SSO, SAML and SCIM, audit log

Create a workspace#

You get a workspace automatically the first time you sign in, named after you (for example "Alex's workspace"). It comes with one API key named Default key, which is also the webhook signing key, and the default concurrency limit of 20.

To add another workspace:

Open the workspace switcher#

Click the workspace card at the top of the sidebar.

Choose Add another workspace#

Enter a name (1 to 80 characters) in the New workspace dialog and click Create workspace.

Start building#

The session switches to the new workspace. You are its admin, and it has its own Default key.

The workspace switcher in the sidebar, listing your workspaces and Add another workspace

The API behind this is POST /auth/create-workspace with { "name": "..." }. It needs a signed-in dashboard session, not an API key. The response includes the new workspace's plaintext API key once, as api_key.

Switch workspaces#

Pick a workspace in the switcher. The dashboard calls POST /auth/switch-workspace with workspace_id, and the session moves to that workspace. Your role can differ per workspace: you might be an admin in one and a member in another. The current role is returned by GET /auth/me together with the list of workspaces you belong to.

API keys never switch. Each key is bound to the workspace that created it.

Workspace settings#

Open Settings, then Workspace. The General section shows:

  • Workspace Name: editable by admins. Saved with PATCH /workspace (name, 1 to 80 characters).
  • Workspace ID: the workspace_id, with a copy button. Support and some integrations ask for it.
Settings, Workspace: the General section with name and workspace ID, and the Users list

PATCH /workspace also accepts webhook_url (the account-level webhook, see Webhooks) and concurrency_limit (1 to 1000, see Limits and concurrency). Only admins can call it.

GET /workspace returns:

{
  "workspace_id": "ws_3f9c2a7d1e4b8c6a5f0d2e19",
  "name": "Harbour Physio",
  "webhook_url": "https://example.com/tried/webhook",
  "concurrency_limit": 20,
  "created_timestamp": 1760668800000
}

Danger zone#

The bottom of Settings, Workspace has a Danger zone with three actions.

Transfer workspace#

Makes another member the owner. The new owner is set to Admin. You can choose Transfer and step down, which changes your own role to Developer. Only admins can transfer. API: POST /workspace/transfer with member_id or email, and optional demote_self. The action is recorded in the audit log as workspace.transfer.

Leave workspace#

Removes your own membership. Rules enforced by the API (POST /workspace/leave):

  • If you are the only member, you cannot leave. Delete the workspace instead.
  • If you are the only admin, transfer the workspace to another member first.
  • Your other sessions in that workspace are signed out. Your current session moves to your next workspace, or signs out if you have none.

Members can leave even though their role is otherwise read-only.

Delete workspace#

Deletes the workspace and everything in it: agents, numbers, calls, contacts and settings. It cannot be undone. Only admins can delete, and you must type the exact workspace name to confirm. API: POST /workspace/delete with { "confirm": "<workspace name>" }.

Important

Deleting a workspace removes call records, recordings references, contacts and keys at once. Export anything you need first from Exports.

Account state#

Each workspace has an account state, shown on Settings, Reliability and, when it is not active, as a banner across the top of the dashboard. See Billing for what each state blocks.

The account banner shown when business verification is needed
Users and rolesInvite teammates and set what they can do.API keysKeys are created per workspace.BillingCredit, budgets and invoices are per workspace.