Teams & Workspaces

Teams let you organize agents, traces, and datasets by group — so your ML team sees their data and your product team sees theirs.

“Team” is the product label for what the SDK and API reference call a workspace — they’re the same entity. When the SDK and API docs say workspace, that’s what this page calls a team.

Key Concepts

Concept	Description
Default team	Auto-created on signup. Cannot be deleted. All members added automatically.
Team members	Users with a role: Admin, Editor, or Viewer.
Active team	The team you’re working in (shown in sidebar). Switch anytime.
Team-scoped data	Agents, traces, datasets belong to the team that created them.

Roles

Each capability is granted per role. A check means the role can do it; a dash means it can’t.

Capability	Viewer	Editor	Admin
View agents, traces, datasets	✓	✓	✓
Use shared skills	✓	✓	✓
Create/edit agents, datasets, skills	—	✓	✓
Run experiments	—	✓	✓
Grade traces, run evaluators, the Playground and AI suggestions (they spend your quota or your provider key)	—	✓	✓
Roll back a manifest, claim a registry skill	—	✓	✓
Export all of the organization’s data	—	—	✓
Invite/remove members	—	—	✓
Change member roles	—	—	✓
Manage team settings (rename, delete)	—	—	✓
Manage billing	—	—	✓

Organization admins can access all teams regardless of membership.

Billing is always at the organization level — only Admins manage it, and changes apply across every team in the org. See Pricing for per-plan limits.

Data Scoping

When you switch teams, you see only that team’s data:

Agents belong to the team where they were created
Traces are routed solely by the API key you send them with (see SDK Integration)
Datasets and experiments belong to the creating team
Skills have their own visibility levels: see Who can see a skill
Billing is always at the organization level

SDK Integration

Behind the scenes, a “team” is the Workspace entity — the UI labels it “Team,” but the SDK and REST reference call it a workspace. There is no team= parameter or DECIMAL_TEAM env var; routing is resolved from your API key alone — the workspace the key is scoped to. The reliable way to route traces to a specific team is a workspace-scoped API key. There is no screen for this: the create dialog in Settings → API keys always mints a global-scoped key, whichever team is active. Workspace scope is set on the API, by passing the team’s workspace id:

curl -X POST https://api.decimal.ai/api/v1/api-keys \
  -H "Authorization: Bearer dai_sk_<your_global_admin_key>" \
  -H "Content-Type: application/json" \
  -d '{"label": "support-team", "scope": "workspace", "workspace_id": "ws_abc123"}'

The global key that authenticates that call is the one you make in Settings → API keys. See Creating a key for the full parameter list. Then point your SDK at the workspace-scoped key it returns:

import decimalai

# All traces sent with this key land in the team that owns the key.
decimalai.init(api_key="dai_sk_...", agent_name="support-agent")

# Or via the environment (the key carries the workspace scope):
export DECIMAL_API_KEY="dai_sk_..."   # a key created under the target team

A key that carries no workspace scope — every key made in the dashboard — resolves to your Default team, so traces sent with it land there regardless of which team you had selected when you created it.

Managing Teams

In the sidebar: Click the team name dropdown to switch or manage teams. In Settings → Teams:

View all teams and members
Create new teams
Invite members, change roles
Rename a team, or delete it from the Danger zone under Team settings (admins only)
The Default team cannot be deleted or renamed

Delete team only works on an empty team. A team that still owns traces, datasets, manifests, skills, experiments, projects, or API keys can’t be deleted — the request comes back naming what’s still in it, so you can move or remove those first. Nothing is cascade-destroyed on your behalf.

Start here

Tutorial: a support agent

Use skills

Manage and measure

Publish a skill

More

Teams & Workspaces

Key Concepts

Roles

Data Scoping

SDK Integration

Managing Teams

Next Steps

Update, pin or fork a skill

Pricing

​Key Concepts

​Roles

​Data Scoping

​SDK Integration

​Managing Teams

​Next Steps

Update, pin or fork a skill

Pricing

Key Concepts

Roles

Data Scoping

SDK Integration

Managing Teams

Next Steps