Skip to main content
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.

​
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).
  • 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).
1

Open the workspace switcher

Click the workspace name in the dashboard header (top-left).
2

Pick + Create new workspace

Give it a name. The new workspace inherits your org’s credits and plan.
3

Switch into it

The switcher routes you to the new workspace. API keys, agents, and the database tab are empty until you populate them.

​
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 for creation, rotation, and revocation.

​
Credit sharing

Credits are org-scoped, not workspace-scoped:
If your org has 100indatacreditsandthreeworkspaces,everyworkspacedrawsfromthesame100 in data credits and three workspaces, every workspace draws from the same 100.
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

Production vs. staging vs. development, all under one billing relationship.
Sales builds in one workspace, engineering builds in another, and they share credits but not agents.
Agencies use one workspace per client to keep audit logs and connections clean.
Spin up a throwaway workspace for an experimental agent that you don’t want polluting the main view.

​
Next steps

Multi-workspace

Switching, the personal workspace, invitations, and claim tokens.

API keys

Create and manage keys for the active workspace.

Credits

Org-level data and AI wallets.

Workspace database

The per-workspace durable state layer.