Team vs Enterprise
Team gives you shared billing and basic administration. Enterprise gives you the controls a security review asks about.
Last verified August 21, 2026
The short answer
If your requirement is "one invoice, SSO, and our data is not used for training", Team covers it. If anyone has asked about audit logs, SCIM, role-based access, data retention or IP allowlisting, you need Enterprise — those are not add-ons to Team.
Can you use both? No — they are alternative business plans, though organisations often start on Team and move up.
Side by side
Option A
Team
$20/seat/month annually for standard seats, $100 for premium (5x usage). Central billing, SSO, admin controls, enterprise search, enterprise desktop deployment, no default model training.
Pick it when
A team wants shared billing and sensible defaults, and nobody has asked for an audit trail yet.
Option B
Enterprise
Self-serve from $20/seat plus API-rate usage, or custom sales-assisted pricing. Adds spend limits, RBAC, SCIM, audit logs, Compliance API, custom retention, network controls, IP allowlisting, HIPAA option and Claude Security.
Pick it when
You have compliance obligations, a formal security review, or need provisioning to be automated rather than manual.
The control gap
| Control | Team | Enterprise |
|---|---|---|
| Central billing | Yes | Yes |
| SSO | Yes | Yes |
| Admin controls | Yes | Yes |
| Enterprise search | Yes | Yes |
| Enterprise desktop deployment | Yes | Yes |
| No default model training | Yes | Yes |
| Spend limits | No | Yes |
| Role-based access | No | Yes |
| SCIM provisioning | No | Yes |
| Audit logs | No | Yes |
| Compliance API | No | Yes |
| Custom data retention | No | Yes |
| Network access control | No | Yes |
| IP allowlisting | No | Yes |
| HIPAA option | No | Yes |
| Claude Security | No | Yes (beta) |
The line falls almost exactly where a security questionnaire falls.
Billing works differently
Team is a flat seat price: $20/seat/month annually for standard, $100 for premium seats with 5x standard usage. Predictable.
Enterprise self-serve is $20 per seat plus API-rate usage costs. That is a different model — you pay for seats and for what is consumed. Budget accordingly; the seat price is not the bill.
Enterprise sales-assisted is custom.
SCIM is the quiet reason people upgrade
Manual provisioning is survivable at 20 people. At 200, with joiners and leavers every week, it stops being an administrative annoyance and becomes a security problem: accounts that should have been deprovisioned and were not.
SCIM is Enterprise-only, and it is often what forces the decision regardless of the other features.
What the plan page does not tell you
Two things that matter more to a real rollout than most of the table above, both documented on the Claude Code side:
- Server-managed settings — permissions and configuration set centrally, not editable by users.
- Managed MCP — controlling which MCP servers your people may connect to.
Without those, developers configure their own tooling and their own external connections. Having Enterprise billing does not change that; configuring these does.
Common misconceptions
- "Enterprise is just Team with a bigger minimum." The billing shape is genuinely different: self-serve Enterprise is per seat plus API-rate usage, where Team is a flat seat price.
- "Team has audit logs." It does not. Audit logs, the Compliance API, SCIM and RBAC are Enterprise.
- "Enterprise means we are compliant." It gives you the controls to demonstrate compliance. Configuring and operating them is still yours.
Sources
- 01Claude pricingOfficialclaude.com
- 02Claude Enterprise PlanOfficialanthropic.com