Organizations and Workspaces
An organization is the top-level account and billing entity in the Anthropic Console. It owns billing, usage limits, and every workspace and member beneath it. Every API key, workspace, and member ultimately belongs to exactly one organization.
A workspace is a grouping mechanism within an organization, typically used to separate spend/usage tracking and access between teams, environments, or projects -- e.g. a "production" workspace and a "staging" workspace, or one workspace per internal team. Workspaces are a Console-level administrative construct: they organize API keys and usage, not conversations or agent context.
Workspaces vs. Claude.ai Projects
This is worth stating plainly because the words sound alike but the products are not: a Console workspace and a Claude.ai Project are different things in different products.
| Console Workspace | Claude.ai Project | |
|---|---|---|
| Product surface | Anthropic Console (developer/API) | Claude.ai (consumer chat) |
| What it groups | API keys, usage, billing attribution | Conversations, files, custom instructions |
| Who uses it | Org admins managing API access | Chat users organizing their own work |
Having a workspace does not create or imply a Project, and vice versa -- they don't share data or configuration.
Source: general, well-established Anthropic Console concepts. Not sourced from a doc file mirrored in this repo (none exists here yet) -- see this site's README for the honesty note on scope.