2 concepts, live from D1
Concepts
Real, well-established Anthropic Console org-admin concepts, grouped by category unless filtered.
| concept | description | distinct from |
|---|---|---|
| How org/workspace structure relates to agent identity and permission policies | Org and workspace structure (this site) governs human administrative access to Console resources — who can create keys, see billing, manage workspaces. It is a separate layer from agent IDENTITY/attribution (which surface an agent acts under, service-account vs. personal-account — see subagentidentities.com) and from agent TOOLSET permission policies (which tools an agent may call and under what default posture — see subagentpermissions.com). An org can contain many workspaces, each of which may host agents running under distinct identities and permission policies. | See subagentidentities.com for agent identity/attribution, and subagentpermissions.com for agent toolset permission policies — this site intentionally does not duplicate either. |
| Workspaces vs. Claude.ai Projects | A common point of confusion: a Console "workspace" and a Claude.ai "Project" are not the same thing. A workspace is an org-admin construct for grouping API keys and usage/billing inside the Anthropic Console (the developer/API surface). A Project in Claude.ai is a user-facing container for conversations, files, and custom instructions inside the consumer/chat product. They live in different products, serve different purposes, and having one does not imply or create the other. | This row exists specifically to call out that distinction explicitly, since the shared word "workspace"/"project" across two related-but-different Anthropic products is an easy mix-up. |
Machine-readable version: GET /api/org-concepts?category=cross_reference