Workspaces

Workspaces provide a way to organize your API usage within an organization. Use workspaces to separate different projects, environments, or teams while maintaining centralized billing and administration.



How workspaces work

Every organization has a Default Workspace that cannot be renamed, archived, or deleted. When you create additional workspaces, you can assign API keys, members, and resource limits to each one.

Key characteristics:

• Workspace identifiers use the wrkspc_ prefix (for example, wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ)
• Maximum 100 workspaces per organization by default (archived workspaces don't count); contact your account team if you need more
• Default Workspace has a wrkspc_ ID like any other workspace (returned in the anthropic-workspace-id response header and accepted by Get Workspace), but it doesn't appear in List Workspaces results, and API keys, usage reports, and cost reports show null for its workspace_id
• API keys are scoped to a single workspace and can only access resources within that workspace



Claude Code workspace

When a member of your organization first signs in to Claude Code with their Claude Console account, Anthropic automatically creates a Claude Code workspace in the organization and adds that member to it. Every subsequent member who signs in to Claude Code is added the same way.

The Claude Code workspace keeps Claude Code traffic separate from your other API workloads:

• Claude Code mints a per-user API key in this workspace at sign-in. You cannot create keys in it manually from the Console.
• A Claude Code key stops working if its owner is removed from the workspace or organization, unlike standard workspace keys.
• Claude Code usage is rate-limited separately, and admins can cap its share of the organization's limits under Settings > Workspaces.
• It is the only workspace that supports per-user monthly spend limits.



Workspace roles and permissions

Members can have different roles in each workspace, allowing fine-grained access control.



Role inheritance

• Organization admins automatically receive Workspace Admin access to all workspaces
• Organization billing members automatically receive Workspace Billing access to all workspaces
• Organization users and developers must be explicitly added to each workspace



Managing workspaces



Using the Console

Create and manage workspaces in the Claude Console.



Create a workspace



Edit workspace details

To modify a workspace's name or color:

1. Select the workspace from the list.
2. Click the ellipsis menu (...) and choose Edit details.
3. Update the name or color and save your changes.



Add members to a workspace

1. Navigate to the workspace's Members tab.
2. Click Add to Workspace.
3. Select an organization member and assign them a workspace role.
4. Confirm the addition.

To remove a member, click the trash icon next to their name.



Set workspace limits

Each workspace's settings split these across two tabs:

• Rate limits: On the Rate limits tab, set limits per model tier for requests per minute, input tokens, or output tokens
• Spend limits: On the Spend limits tab, cap monthly spending and configure alerts when spending reaches certain thresholds



Archive a workspace

To archive a workspace, click the ellipsis menu (...) and select Archive. Archiving:

• Preserves historical data for reporting
• Deactivates the workspace and all associated API keys
• Cannot be undone