Skip to navigation

Teamspace context

Keep work in the correct workspace and teamspace.
View as Markdown

A workspace is the account boundary associated with your API key. A teamspace (also called a Space) separates work inside that workspace. Use profiles to change workspaces and teamspace context to select a Space.

1. Inspect your available context

simplified auth:whoami
simplified teamspace:current

auth:whoami identifies the workspace and teamspaces available to the key. teamspace:current shows the context selected for CLI requests and where that selection came from.

2. Save an alias

Copy an accessible numeric teamspace ID from auth:whoami. Save it under a name you can recognize:

simplified teamspace:add marketing 12345
simplified teamspace:list

Replace 12345 with the real ID. An alias is a local shortcut; creating it does not create a teamspace or change your permissions.

3. Select a teamspace

simplified teamspace:use marketing
simplified teamspace:current
simplified accounts:list

The selection is saved for subsequent commands. You can also pass a numeric ID directly to teamspace:use.

Return to the default workspace context with:

simplified teamspace:use default

Override context for one command

simplified accounts:list --teamspace marketing
SIMPLIFIED_TEAMSPACE_ID=12345 simplified projects:list --type pm

These overrides do not change the saved selection. Context is resolved in this order: --teamspace, then SIMPLIFIED_TEAMSPACE_ID, then the saved selection, then the default workspace.

For scripts that always target one teamspace, pass its ID explicitly. This avoids depending on the last context selected in an interactive terminal.

Switch workspaces

simplified auth:use client-acme
simplified teamspace:use default
simplified auth:whoami

Then select an accessible teamspace for that workspace. Switching a teamspace never switches the API key or gives access to another workspace.

Remove a shortcut you no longer use with simplified teamspace:remove marketing. This removes the local alias, not the teamspace itself.

If a request fails with 403, verify that the key can access the selected teamspace. A malformed ID can produce 400. The CLI does not silently retry against a different workspace when access fails.