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

# Workspaces

> The unit of tenancy in agntdata — what a workspace owns, and how it sits inside an organization.

A **workspace** is the unit of tenancy in agntdata. Everything you build lives inside one — API keys, deployed agents, schedules, webhooks, connections, the workspace database, the audit log. An **organization** sits one level above and owns the billing relationship: credits, the active feature plan, the trial, payment methods.

This page covers what a single workspace owns. For switching between workspaces, the personal-workspace lifecycle, and how invitations work, see **[Multi-workspace](/concepts/multi-workspace)**.

## What a workspace owns

```
Organization (billing)
└── Workspace
    ├── API keys (one workspace, many keys)
    ├── Members (workspace-scoped, with roles)
    ├── Deployed agents
    ├── Schedules, webhooks, escalation inbox
    ├── Connections (BYOK + OAuth installs)
    ├── Workspace database (dedicated Supabase project)
    └── Usage logs (per-tool, per-call)
```

Workspaces are the boundary that matters for:

* **Access control** — `workspace_members` decides who sees what. Every workspace-scoped table is RLS-gated by `is_workspace_member(workspace_id)`.
* **Isolation** — the workspace database is its own Supabase project; there's no shared schema across workspaces.
* **Audit attribution** — every usage log row, every escalation, every agent session belongs to exactly one workspace.

## What the organization owns

The organization sits above workspaces and owns:

* **Credit wallets** — one data wallet, one AI wallet, both shared across every workspace in the org.
* **Subscription** — the active feature plan (Build / Launch / Scale) lives on the org.
* **Trial** — one trial per org, ever (see [Trial](/billing/trial)).
* **Auto-reload settings** — configured per-wallet at the org level.
* **Payment methods** — Stripe customer is the org, not the workspace.

You'll see this split reflected in the dashboard: the workspace switcher is in the header; the Billing tab shows org-level numbers regardless of which workspace is selected.

## Creating a workspace

When you sign up, agntdata creates a **Personal** workspace automatically. You can create additional workspaces if your plan allows it (Build: 1, Launch: 3, Scale: unlimited).

<Steps>
  <Step title="Open the workspace switcher">
    Click the workspace name in the dashboard header (top-left).
  </Step>

  <Step title="Pick + Create new workspace">
    Give it a name. The new workspace inherits your org's credits and plan.
  </Step>

  <Step title="Switch into it">
    The switcher routes you to the new workspace. API keys, agents, and the database tab are empty until you populate them.
  </Step>
</Steps>

## API keys

Each API key belongs to exactly one workspace. Requests authenticated with that key are scoped to its workspace — you don't pass a workspace id on the request. You can create many keys per workspace (e.g. one per environment) and they all draw on the same org-level credit wallets.

See [API keys](/authentication/api-keys) for creation, rotation, and revocation.

## Credit sharing

Credits are org-scoped, not workspace-scoped:

<Info>
  If your org has $100 in data credits and three workspaces, every workspace draws from the same $100.
</Info>

This is intentional:

* **Simplified billing** — one wallet per org, regardless of how you slice it into workspaces.
* **Shared limits** — your plan's RPM and webhook event quotas apply to the whole org.
* **Centralized monitoring** — the Billing tab tells you total spend across all workspaces.

If you need separate billing per project, create separate organizations (i.e. separate accounts).

## When to use multiple workspaces

<AccordionGroup>
  <Accordion title="Environment isolation">
    Production vs. staging vs. development, all under one billing relationship.
  </Accordion>

  <Accordion title="Team separation">
    Sales builds in one workspace, engineering builds in another, and they share credits but not agents.
  </Accordion>

  <Accordion title="Client work">
    Agencies use one workspace per client to keep audit logs and connections clean.
  </Accordion>

  <Accordion title="Experiments">
    Spin up a throwaway workspace for an experimental agent that you don't want polluting the main view.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Multi-workspace" icon="building" href="/concepts/multi-workspace">
    Switching, the personal workspace, invitations, and claim tokens.
  </Card>

  <Card title="API keys" icon="key" href="/authentication/api-keys">
    Create and manage keys for the active workspace.
  </Card>

  <Card title="Credits" icon="coins" href="/billing/credits">
    Org-level data and AI wallets.
  </Card>

  <Card title="Workspace database" icon="database" href="/agents/workspace-database">
    The per-workspace durable state layer.
  </Card>
</CardGroup>