Workspaces

Organize API keys, manage team access, and control costs with 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 (archived workspaces don't count)
• Default Workspace has no ID and doesn't appear in list endpoints
• 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

1. Open workspace settings

   In the Claude Console, go to Settings > Workspaces.

2. Create a workspace

   Click Create workspace.

3. Configure the workspace

   Enter a workspace name and select a color for visual identification.

4. Create the workspace

   Click Create to finalize.

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

In the Limits tab, you can configure:

• Rate limits: Set limits per model tier for requests per minute, input tokens, or output tokens
• Spend notifications: 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

Using the Admin API

Programmatically manage workspaces using the Admin API.

# Create a workspace
curl --request POST "https://api.anthropic.com/v1/organizations/workspaces" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY" \
  --data '{"name": "Production"}'

# List workspaces
curl "https://api.anthropic.com/v1/organizations/workspaces?limit=10&include_archived=false" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"

# Archive a workspace
curl --request POST "https://api.anthropic.com/v1/organizations/workspaces/{workspace_id}/archive" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"

For complete parameter details and response schemas, see the Workspaces API reference.

Managing workspace members

Add, update, or remove members from a workspace:

# Add a member to a workspace
curl --request POST "https://api.anthropic.com/v1/organizations/workspaces/{workspace_id}/members" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY" \
  --data '{
    "user_id": "user_xxx",
    "workspace_role": "workspace_developer"
  }'

# Update a member's role
curl --request POST "https://api.anthropic.com/v1/organizations/workspaces/{workspace_id}/members/{user_id}" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY" \
  --data '{"workspace_role": "workspace_admin"}'

# Remove a member from a workspace
curl --request DELETE "https://api.anthropic.com/v1/organizations/workspaces/{workspace_id}/members/{user_id}" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"

For complete parameter details, see the Workspace Members API reference.

API keys and resource scoping

API keys are scoped to a specific workspace. When you create an API key in a workspace, it can only access resources within that workspace.

Resources scoped to workspaces include:

• Files created through the Files API
• Message Batches created through the Batch API
• Skills created through the Skills API

Some resources are managed at the organization level and cannot be managed with a workspace API key:

• MCP tunnels are created in a workspace; the Console MCP tunnels list and the Managed Agent server picker show tunnels in the current workspace only, while the cap of 10 active tunnels applies organization-wide. Tunnel management requires a role with tunnel management permissions; organization developers can view but not change them. The Tunnels API authenticates with a short-lived OAuth token carrying the org:manage_tunnels scope, obtained through Workload Identity Federation, not a workspace API key.
• Workspaces themselves and organization members are managed through the Admin API, which requires an Admin API key.

Workspace limits

You can set custom spend and rate limits for each workspace to protect against overuse and ensure fair resource distribution.

Setting workspace limits

Workspace limits can be set lower than (but not higher than) your organization's limits:

• Spend limits: Cap monthly spending for a workspace
• Rate limits: Limit requests per minute, input tokens per minute, or output tokens per minute

For detailed information on rate limits and how they work, see Rate limits. You can also read your current organization and workspace rate limits programmatically with the Rate Limits API.

Usage and cost tracking

Track usage and costs by workspace using the Usage and Cost API:

curl "https://api.anthropic.com/v1/organizations/usage_report/messages?\
starting_at=2025-01-01T00:00:00Z&\
ending_at=2025-01-08T00:00:00Z&\
workspace_ids[]=wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ&\
group_by[]=workspace_id&\
bucket_width=1d" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"

Usage and costs attributed to the Default Workspace have a null value for workspace_id.

Common use cases

Environment separation

Create separate workspaces for development, staging, and production:

Team or department isolation

Assign workspaces to different teams for cost allocation and access control:

• Engineering team with developer access
• Data science team with their own API keys
• Support team with limited access for customer tools

Project-based organization

Create workspaces for specific projects or products to track usage and costs separately.

Best practices

1. Plan your workspace structure

   Consider how you'll organize workspaces before creating them. Think about billing, access control, and usage tracking needs.

2. Use meaningful names

   Name workspaces clearly to indicate their purpose (for example, "Production - Customer Chatbot", "Dev - Internal Tools").

3. Set appropriate limits

   Configure spend and rate limits to prevent unexpected costs and ensure fair resource distribution.

4. Audit access regularly

   Review workspace membership periodically to ensure only appropriate users have access.

5. Monitor usage

   Use the Usage and Cost API to track workspace-level consumption.

FAQ

What's the Default Workspace?

Every organization has a "Default Workspace" that cannot be edited, renamed, or removed. This workspace has no ID and doesn't appear in workspace list endpoints. Usage attributed to the Default Workspace shows a null value for workspace_id in API responses.

What's the Claude Code workspace?

Anthropic creates the Claude Code workspace automatically the first time a member of your organization signs in to Claude Code with their Console account. It isolates Claude Code's API keys, usage, and rate limits from your other workloads. See Claude Code workspace for details.

Are there limits on workspaces?

Yes, you can have a maximum of 100 workspaces per organization. Archived workspaces do not count toward this limit.

How do organization roles affect workspace access?

Organization admins automatically get the Workspace Admin role in all workspaces. Organization billing members automatically get the Workspace Billing role. Organization users and developers must be manually added to each workspace.

Which roles can be assigned in workspaces?

Organization users and developers can be assigned Workspace Admin, Workspace Developer, Workspace Limited Developer, or Workspace User roles. The Workspace Billing role cannot be manually assigned; it's inherited from having the organization billing role.

Can organization admin or billing members' workspace roles be changed?

Only organization billing members can have their workspace role upgraded to an admin role. Otherwise, organization admins and billing members cannot have their workspace roles changed or be removed from workspaces while they hold those organization roles. Their workspace access must be modified by changing their organization role first.

What happens to workspace access when organization roles change?

If an organization admin or billing member is demoted to user or developer, they lose access to all workspaces except ones where they were manually assigned roles. When users are promoted to admin or billing roles, they gain automatic access to all workspaces.

What happens to API keys when a user is removed from a workspace?

API keys persist in their current state as they are scoped to the organization and workspace, not to individual users. The exception is the Claude Code workspace, where each key is bound to the member who created it and stops working when that member is removed.

See also

• Admin API
• Admin API reference
• Rate limits
• Usage and Cost API