Understanding Claude's Plan Tiers: Free, Pro, Team, and Enterprise
Anthropic offers Claude across four plan tiers: Free, Pro, Team, and Enterprise.
//
Search across all documentation pages
Anthropic offers Claude across four plan tiers: Free, Pro, Team, and Enterprise.
Each tier answers a different question: how many people need access, and how much administrative control does the organization need over that access.
For an individual, the choice is mostly about usage limits and model access.
For an admin evaluating a company-wide rollout, the choice is really about seats, governance controls, and how much of the workspace/seat/role model described elsewhere in this section is actually available to use.
Free is a single-user tier with no workspace or seat concept in any meaningful sense.
It exists for individuals trying Claude for personal use, with the tightest usage limits of the four tiers.
Pro is also single-user, but with materially higher usage limits and access to more of Claude's model lineup.
Pro is a good fit for an individual professional who relies on Claude daily but does not need to manage anyone else's access.
Team is the first tier where the workspace/seat/role model becomes real.
A Team workspace supports multiple seats, an admin role that can invite and manage members, and shared billing across the group.
Enterprise builds on everything Team offers and adds the governance layer that larger organizations need: single sign-on (SSO) tied to the company's identity provider, SCIM provisioning for automated seat lifecycle management, and programmatic access to per-user cost and usage data through the Enterprise Analytics API.
A simple way to hold these four tiers in mind: Free and Pro are about an individual's access to Claude, while Team and Enterprise are about an organization's ability to manage many people's access to Claude at once, with Enterprise adding the automation and oversight a large organization eventually needs.
Seats and workspaces only start to matter once you cross from Pro into Team.
Below that line, the "workspace" concept barely applies because there is only ever one person to manage.
Above that line, an admin has to make real decisions: how many seats to buy, who gets the admin role, and how invites and removals get handled as people join and leave.
Team handles seat lifecycle manually.
An admin invites each new person and removes each departing person by hand through the Members screen.
This works well for smaller teams but becomes a real operational burden once headcount grows into the hundreds, which is exactly the gap Enterprise closes.
Enterprise's SSO and SCIM provisioning connect the workspace to the company's existing identity provider, so seat creation and removal can track the company directory automatically instead of relying on an admin to remember every change.
This is the single biggest functional jump between Team and Enterprise: it is less about raw usage limits and more about who, or what system, is responsible for keeping seat access accurate over time.
The Enterprise Analytics API is the other major Enterprise-only capability.
It gives admins programmatic access to per-user cost, usage, and engagement data across every Claude surface, including chat, Claude Code, Cowork, and Office agents, which Team admins can only see through the console's built-in usage screens rather than pulling into their own systems.
The decision between Team and Enterprise is rarely just about price.
It is about whether the organization already has (or is willing to invest in) an identity provider integration and whether finance or engineering leadership wants raw, per-user usage data to build their own cost dashboards, rather than relying on the console's built-in views.
A fast-growing startup with 15 people might comfortably run on Team for over a year, manually inviting new hires, before the operational cost of manual seat management justifies moving to Enterprise.
A larger company that already runs SSO for every other tool in its stack often moves to Enterprise immediately, simply to keep Claude consistent with how every other application handles access.
| Tier | Strength | Weakness | Best Fit |
|---|---|---|---|
| Free | No cost, easy to try | Tightest usage limits, no team features | Individuals exploring Claude for the first time |
| Pro | Higher usage limits, full model access for one person | Still single-user, no seat management | Individual professionals with daily, personal usage |
| Team | Multi-seat workspace, admin role, shared billing | Manual seat lifecycle, no SSO/SCIM/analytics API | Smaller teams without an identity provider requirement |
| Enterprise | SSO, SCIM automation, programmatic analytics access | Highest cost, requires IT coordination to set up SSO | Larger organizations that need governance and audit-ready access control |
Cost attribution is where the tier choice compounds over time.
On Team, an admin can see workspace-level billing but has to rely on the console's usage screens to understand who is driving cost.
On Enterprise, the Analytics API lets a finance or platform team pull per-user cost data directly, which becomes increasingly valuable as seat counts grow into the hundreds and manual review of the console's usage screens stops scaling.
Both are single-user tiers with no workspace or seat management. Pro offers materially higher usage limits and broader access to Claude's model lineup than Free.
As soon as more than one person needs managed access with shared billing, invite/remove control, and an admin role. Pro has no mechanism for managing anyone else's access.
No. Team supports genuinely multi-seat workspaces; the practical limit that pushes companies toward Enterprise is usually the operational burden of manual seat management, not a hard cap.
Mainly to automate seat lifecycle through SSO/SCIM and to get programmatic, per-user cost and usage data instead of relying on the console's built-in usage screens.
Usually yes, since configuring SSO requires coordinating with whoever manages the company's identity provider. This is a real setup cost worth planning for before committing to the migration.
Yes. A person can be invited into a Team or Enterprise workspace as a seat regardless of whatever personal Free or Pro account they may have used previously.
It gives Enterprise admins programmatic access to per-user cost, usage, and engagement data across every Claude surface, useful for cost attribution and tracking adoption across a large organization.
Both support shared, workspace-level billing with a dedicated billing role. Enterprise adds the ability to break that spend down programmatically per user via the Analytics API.
Model access can vary by tier, with higher tiers generally offering broader access to the full model lineup, so it is worth checking current model availability per tier before assuming parity.
Assuming the decision is only about seat count or price. In practice, the meaningful jump from Team to Enterprise is about governance and automation, not just how many people can be invited.
Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.
Reviewed by Chris St. John·Last updated Jul 16, 2026