It depends on what data Claude will touch. Claude Team is for teams that need to control who gets in and which features they use, without regulated customer data: an agency, a marketing department, a development team. Claude Enterprise is for banks, credit unions, insurers, health organizations and anyone working with customer, member or patient data. Personal accounts don't qualify for either.
The difference isn't what Claude can do, which is nearly the same on both plans. It's what your organization can control and, above all, prove.
What plans does Claude offer?
As of October 2026, per Anthropic's pricing page:
| Plan | Who it's for | What matters to an organization |
|---|---|---|
| Free, Pro and Max | Individuals | Personal accounts under consumer terms. Each user decides whether their chats train models; if they allow it, data is kept up to 5 years. The organization manages nothing |
| Team | Teams of 2 to 150 | Central administration: access, features, connectors, spend and usage analytics |
| Enterprise | Organizations that must show controls to an auditor or examiner | Everything in Team, plus audit logs, retention, roles, network controls and the HIPAA-ready option |
| API | Developers | For building your own systems, such as agents or automations. A separate conversation |
Team and Enterprise run under Anthropic's commercial terms, which bar it from training models on customer content. Personal accounts don't.
Who is Claude Team for, and what does it control?
Team is a real business plan, not a bigger personal account. It's for teams that want clear rules and visibility but won't put regulated customer or patient data into Claude. At Andes we use Claude Team, with a written rule: no customer personal data goes into prompts.
What a Team admin can control:
| Area | What you can do on Team |
|---|---|
| Access | Single sign-on, domain verification, and a block on new personal accounts opened with the company email |
| Features | Turn off web search, code execution and file creation, Cowork and Claude in Chrome for the whole organization |
| Connectors | Only owners add custom connectors, with a per-tool permission ceiling and an allowlist for desktop extensions |
| Claude Code | Central rules from the admin console: allowed and denied commands, blocked sensitive files, approved servers |
| Behavior | Organization-wide instructions and skills |
| Training | Turn off feedback (the Rate chats setting) so no conversation ends up in training |
| Spend | Limits per user and for the organization |
| Visibility | Per-member usage analytics and a per-user spend report covering the last 90 days. The Primary Owner can export the organization's data, including conversations |
An honest caveat: Claude Code rules sent from the console run on each person's machine. Anthropic notes that on a device the organization doesn't manage, a user can get around them; on managed devices, the protection is stronger.
Who is Claude Enterprise for, and what does it add?
Enterprise is for supervised institutions and for any organization that will work with customer, member or patient data in Claude. What it adds over Team is the ability to show an examiner or auditor who did what, how long data is kept, and where access comes from.
| Enterprise-only control | What it does | Why it matters at a regulated institution |
|---|---|---|
| Audit logs and Compliance API | Exports 180 days of events (sign-ins, invites, project and settings changes) and feeds activity into your monitoring systems | You can answer who did what and when, and keep the evidence as long as your rules require |
| Custom data retention | Sets how long conversations are kept, from 30 days | Retention is your decision, not a default |
| Role-based permissions | Sets which teams can use Claude Code, web search or each connector | Each team gets only what it needs, not the same for everyone |
| Automated provisioning (SCIM) | Adds and removes users from your directory | Access can end as soon as someone is removed from your directory |
| Domain capture | Claims existing personal accounts on your email domain and migrates them into the organization's account | Existing personal accounts on your domain move under the organization |
| IP allowlisting and tenant restrictions | Allows access only from your networks and blocks other organizations' accounts on your corporate network | You can limit access to networks you control and block other accounts on your network |
| HIPAA-ready option | Turns on a business associate agreement (BAA) for health data | Required before PHI goes anywhere near Claude |
How do you choose between Team and Enterprise?
Five questions. A yes to any of the first four means Enterprise:
| Question | If the answer is yes |
|---|---|
| Will your team put customer, member or patient data into Claude? | Enterprise |
| Can an examiner, auditor or parent company ask you who did what, and when? | Enterprise |
| Do you need different rules for different teams, such as connectors for IT only? | Enterprise |
| Do you need to set how long conversations are kept? | Enterprise |
| Do you only need to control who gets in, which features are used and how much is spent? | Team |
Why don't personal accounts ever qualify?
Because the organization can't see, configure or close anything. On a personal account:
- The terms are consumer terms, not commercial.
- The user, not the organization, decides whether chats train models.
- There's no record of what was shared or with whom.
- When the person leaves, the data leaves with them.
A paid personal account is still personal. What the user pays for is more capacity, not control for the organization.
What do you still have to configure, on either plan?
No plan is safe just because you bought it:
- Block new personal accounts on the company email once the domain is verified. On Team and Enterprise.
- Turn off feedback with the Rate chats setting, so no rated conversation ends up in training. On Team and Enterprise.
- Turn on only the features and connectors you need. Connecting Claude to other systems is useful, and it's also where most data leaves.
- Set retention. On Enterprise, data is kept indefinitely unless you set a period.
- Review the logs. Enterprise audit exports cover 180 days and include conversation IDs, not content; for longer, use the Compliance API.
An honest caveat for health care: Enterprise's HIPAA-ready setup doesn't cover every feature, only the Primary Owner can turn it on, and the decision can't be reversed.
What do US regulators expect?
No US banking or health regulator names Claude or any specific AI tool. What they already expect points to Enterprise once customer data is involved:
- Banks: the interagency guidance on third-party relationships (OCC Bulletin 2023-17) expects due diligence and ongoing monitoring of vendors. An audit trail and retention you control are what make monitoring possible.
- Credit unions: NCUA says it has no AI-specific rules, and that examiners review internal controls around AI tools and third-party due diligence.
- Health organizations: PHI needs a business associate agreement. Anthropic offers one on HIPAA-ready Enterprise plans, not on Team.
- Data location: Anthropic says commercial data is stored in the US and that traffic may be routed to other countries; Enterprise customers on usage-based billing can ask for US-only processing.
How much do they cost?
As of October 2026, Anthropic lists Team from $20 per seat per month billed annually ($25 billed monthly), and Enterprise from $20 per seat per month billed annually plus usage at API rates. Anthropic notes that prices and plans can change, so confirm the current quote before you budget.
How do we handle it at Andes?
We work with Claude every day and roll it out for companies: we pick the plan based on the data it will touch, set up access, features, connectors, retention and logs, connect Claude to the systems you already use, and train the team. If you don't yet know which AI tools your staff use, start with how to control shadow AI, and for marketing use, see who approves AI-generated marketing.
Do you know which plan your team needs?
If personal accounts and a Team plan live side by side today and nobody knows what data goes into each, let's talk. See our AI for regulated institutions service and let's start by sorting out the accounts.
Sources
- Claude, Plans and pricing: https://claude.com/pricing
- Claude Help Center, Roles and permissions: https://support.claude.com/en/articles/9267276-roles-and-permissions
- Claude Help Center, View usage analytics for Team and Enterprise plans: https://support.claude.com/en/articles/12883420-view-usage-analytics-for-team-and-enterprise-plans
- Claude Help Center, Export your organization's data: https://support.claude.com/en/articles/13346720-export-your-organization-s-data
- Claude Help Center, Get started with custom connectors using remote MCP: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
- Claude Code Docs, Configure server-managed settings: https://code.claude.com/docs/en/server-managed-settings
- Claude Privacy Center, Configure custom data retention controls for Enterprise plans: https://privacy.claude.com/en/articles/10440198
- Claude Help Center, Access audit logs: https://support.claude.com/en/articles/9970975
- Claude Help Center, Restrict access to Claude with IP allowlisting: https://support.claude.com/en/articles/13200993
- Claude Help Center, Enforce network-level access control with Tenant Restrictions: https://support.claude.com/en/articles/13198485-enforce-network-level-access-control-with-tenant-restrictions
- Claude Help Center, HIPAA-ready Enterprise plans: https://support.claude.com/en/articles/13296973
- Claude Privacy Center, Is my data used for model training?: https://privacy.claude.com/en/articles/7996868
- Claude Privacy Center, Where are your servers located?: https://privacy.claude.com/en/articles/7996890
- Claude Help Center, Claim and migrate accounts on your domain: https://support.claude.com/en/articles/14625619-claim-and-migrate-accounts-on-your-domain
- Anthropic, Updates to our Consumer Terms and Privacy Policy (August 2025): https://www.anthropic.com/news/updates-to-our-consumer-terms
- OCC Bulletin 2023-17, Third-Party Relationships: Interagency Guidance on Risk Management: https://www.occ.gov/news-issuances/bulletins/2023/bulletin-2023-17.html
- NCUA, Artificial Intelligence (AI): https://ncua.gov/regulation-supervision/regulatory-compliance-resources/artificial-intelligence-ai