A workspace is the primary boundary for data, permissions, API keys, agents, integrations and usage.

​
Workspace types

TypePurposeBilling owner
StandardRegular company or team workspaceItself
AgencyManages its own agents and client workspacesItself
ClientIsolated customer or project workspace under an agencyParent agency
Client workspaces separate agents, deployments, runs, files, integrations and members while preserving centralized agency billing.

​
What belongs to a workspace

ResourceNotes
Agents and deploymentsStable agents with immutable versions
API keysAccount-scoped programmatic authority
Runs and responsesDurable runtime execution records
Files and artifactsAuthorized run outputs
IntegrationsSlack, Teams and workspace-level operations settings
MembersUsers and workspace permissions
UsageAttributed to the originating workspace
BillingManaged by the billing-owner workspace

​
Billing ownership

Runtime access is checked against: 
standard workspace -> itself
agency workspace   -> itself
client workspace   -> parent agency
Client workspaces do not manage billing directly. Their usage is attributed to the client where supported and charged to the agency billing owner.

​
Authority

User actions and API keys are limited to their workspace. Use separate keys per integration and environment. A key created in one workspace cannot call an agent belonging to another workspace. Billing, member management, API-key management, integrations and operations settings require the corresponding workspace permission.