> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decimal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams & Workspaces

> Organize agents, traces, and skills by team with role-based access.

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

<Note>
  "Team" is the product label for what the SDK and [API reference](/sdk/python/init) call a **workspace** — they're the same entity. When the SDK docs say `project`/`workspace`, that's the same scope this page calls a team.
</Note>

## 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  |    —   |    ✓   |   ✓   |
| Edit eval policies                    |    —   |    ✓   |   ✓   |
| Run experiments                       |    —   |    ✓   |   ✓   |
| Invite/remove members                 |    —   |    —   |   ✓   |
| Change member roles                   |    —   |    —   |   ✓   |
| Manage team settings (rename, delete) |    —   |    —   |   ✓   |
| Manage billing                        |    —   |    —   |   ✓   |

Organization admins can access all teams regardless of membership.

<Note>
  **Billing** is always at the organization level — only Admins manage it, and changes apply across every team in the org. See [Pricing](/pricing) for per-plan limits.
</Note>

## 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 by the API key you send them with — and, if set, the `project` you pass to `init()` (see [SDK Integration](#sdk-integration))
* **Datasets** and **experiments** belong to the creating team
* **Skills** have their own visibility rules (see below)
* **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** and, if set, the **`project`** you pass to `init()` (sent as the `X-Decimal-Project` header).

The reliable way to route traces to a specific team is a **workspace-scoped API key** — create one in **Settings → API Keys** while that team is active, then point your SDK at it:

```python theme={null}
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")
```

```bash theme={null}
# 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 created without a specific team active belongs to your **Default team**, so traces sent with it land there.

## 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 or delete teams (admins only)
* The Default team cannot be deleted or renamed

***

## Skill Visibility

Every skill has a visibility level set at creation time:

| Level            | Who can see                | Who can edit               |
| ---------------- | -------------------------- | -------------------------- |
| **Organization** | Everyone in your org       | Creator + editors + grants |
| **Team**         | Members of the owning team | Creator + editors + grants |
| **Personal**     | Only the creator           | Only the creator + grants  |

The default visibility for new skills is **Organization** (maximum discoverability).

### Sharing Skills

For Team and Personal skills, share access without changing visibility:

1. Open the skill → **Settings** tab
2. In **Sharing & Access**, click **"+ Share"**
3. Choose a team or person
4. Set access: **View** (use the skill) or **Edit** (modify it)

### Cloning Skills

When you clone a skill:

* Gets its own name (you choose)
* Copies the latest version's content
* Owned by your current team
* Inherits the original's visibility
* Fully independent — edits don't affect the original

### Important Notes

* **Visibility is permanent.** Once set, it cannot be changed. Clone the skill if you need a different level.
* **Organization skills don't need sharing.** Everyone can already see them.
* **Skills follow the team.** Adding someone to a team gives them access to Team-visible skills automatically.

## Next Steps

<CardGroup cols={2}>
  <Card title="Skills Guide" icon="puzzle-piece" href="/guides/skills">
    Create, version, and publish skills.
  </Card>

  <Card title="Pricing" icon="credit-card" href="/pricing">
    Per-plan member and workspace limits.
  </Card>
</CardGroup>