AI Codex
AdministrationRole-Specific

Claude Team vs. Enterprise: the actual differences, for IT and legal

In brief

Scannable side-by-side: data handling, compliance, identity, admin controls, and retention. Written to be shared with legal without edits.

6 min read·

Contents

Sign in to save

When Priya forwards her Claude business case to her VP, and the VP forwards it to IT, this is the next thing IT needs. Not a sales-page feature grid — a straight read on what actually differs for compliance, identity, and data handling.

The numbers below are accurate as of April 2026. Anthropic publishes current details at claude.com/pricing and trust.claude.com — verify before signing anything.

The short version

Both plans do not train on your data. That's the single most common question and it has the same answer on both tiers: Anthropic does not train Claude on inputs or outputs from any paid plan, Team or Enterprise.

Team is built for one department or small company — shared Projects, basic admin, SSO via Google/Microsoft only, 30-day default retention. Most mid-size teams never need more than this.

Enterprise adds the controls IT needs at scale — SAML/SCIM, audit logs, Compliance API, custom retention, role-based access, per-user spend caps, BAA/HIPAA, data residency options, and a real DPA with custom terms.

If you can answer "yes" to any of these, you want Enterprise, not Team:

  • We need SSO/SAML with our IdP (Okta, Azure AD, etc.)
  • We need automated user provisioning (SCIM)
  • We need audit logs for compliance review
  • We're in healthcare and need a BAA for HIPAA
  • We need data residency outside the US
  • We need role-based permissions beyond "admin vs. user"
  • We need per-user spend limits or usage analytics by group

Everything else is better at Team's price point.

Side-by-side: what actually differs

Dimension Team Enterprise
Training on customer data No No
Default data retention 30 days Configurable (customer-defined)
SSO Google / Microsoft only SAML / any IdP
User provisioning Manual invite SCIM (automated)
Audit logs Basic admin activity Full audit log + Compliance API
Role-based access Admin / user Granular roles + user groups
Per-user spend caps No Yes
Usage analytics Per workspace Per user, per group, per feature
BAA for HIPAA No Yes (request during contracting)
Data residency US US + other regions on request
DPA / custom terms Standard MSA Negotiable DPA and terms
MCP / connector policy controls Per-workspace toggle Managed policies enforced org-wide
Claude Code usage analytics Limited Full (per-user, per-repo)
Support Email / help center Named account team, SLAs

What this means for common compliance questions

"Is our data used to train future models?"
No, on either plan. This is a contractual commitment across Team and Enterprise.

"Where is our data processed and stored?"
Team: US regions. Enterprise: US by default, with data residency options (EU, other) available on request during contracting. Processing regions are listed in Anthropic's sub-processor documentation.

"How long is data retained?"
Team: 30 days by default, then purged. Enterprise: configurable — you can set retention to zero (no retention beyond the request) or extend it for audit purposes.

"Can we get an audit log of what users did?"
Team has basic admin activity logs. Enterprise has a full audit log plus a Compliance API that lets you query user activity, conversations, and admin changes programmatically — the same pattern you'd use with any enterprise SaaS auditing tool.

"Do you sign a BAA for HIPAA?"
Enterprise only. Request it during the contracting process, not after signing the MSA.

"What do our users have access to, and can we lock it down?"
Both plans let admins toggle connectors and Claude Code at the workspace level. Enterprise adds role-based access, user groups (managed via SCIM or manually), and managed policies that enforce MCP / tool permissions across the org — users cannot toggle around them.

"Can we cap spend per user?"
Enterprise only. Team does per-workspace billing; per-user caps require Enterprise.

"Can we integrate with our SIEM?"
Enterprise — via the Compliance API and the audit log export.

The pricing question nobody wants to ask

Team is public pricing ($30/user/month). Enterprise is custom, typically starting around $60/user/month for small deployments and scaling down per-seat for larger commitments. Anthropic will usually quote quickly if you already have headcount and a timeline.

The hidden cost nobody flags: an organization on Team that grows past ~200 users usually ends up needing SSO/SCIM for operational reasons (people come and go, manual provisioning breaks). At that point, you're moving to Enterprise anyway. If you know you're going to cross 200 users in the next 12 months, start on Enterprise.

When Team is the right call (even at scale)

Not every large organization needs Enterprise on day one. Team is the right choice when:

  • A single department wants to roll out Claude ahead of the rest of the org
  • You want to pilot without a long contracting cycle
  • Your IdP isn't SAML-based or SCIM is already handled elsewhere
  • You don't yet need audit-grade compliance (no HIPAA, no SOC 2 customer asks, no data residency requirements)

Many companies run Team for a department for 6 months, learn what they actually need, and then move to Enterprise with a clear set of requirements. This is a cleaner path than over-contracting upfront.

What to bring to your internal review

If IT or legal is reviewing Claude for approval, this is the packet:

  1. Anthropic's trust center — SOC 2 Type II, GDPR, ISO 27001 documentation
  2. The Data Processing Agreement (Team) or a negotiated DPA (Enterprise)
  3. The Acceptable Use Policy — content that's out of bounds
  4. This comparison table (save the page and forward it)

Try this today

If you're the person building the case for your org: copy the "side-by-side" table above into a one-page PDF. Add two columns next to it — one for "our current tool" and one for "our requirement." Fill in what you already use and what you actually need. That document goes to IT, not a sales deck.


The business case guide covers the pitch. The IT approval guide covers what IT asks for. This is the reference document that answers their questions once they're engaged.

Further reading

Related tools

Weekly brief

For people actually using Claude at work.

Each week: one thing Claude can do in your work that most people haven't figured out yet — plus the failure modes to avoid. No tutorials. No hype.

No spam. Unsubscribe anytime.

What to read next

Picked for where you are now

All articles →