Short answer
Claude for Enterprise is the plan for organizations that need central administration and extra security and compliance controls on top of everything in Team. On CoworkStrategy.com I walk the setup in order, using only what Anthropic’s help article says.
I wrote this for the owner who has already counted heads and knows the company clears the bar. If you are still weighing the features, my guide to what each security control is for comes first. This page covers the order of work: who you appoint, what you verify, what you connect and what you decide before the first colleague signs in.
| Setup item | What Anthropic’s page says | Where it sits in the order |
|---|---|---|
| Self-serve seat minimum | Plans require a minimum of 20 seats, per Anthropic’s seat article. | Step 1, choose how you buy |
| Sales-assisted seat minimum | The minimum is 50 on that route, per Anthropic’s plan overview. | Step 1, choose how you buy |
| What the seat includes | Claude on web, desktop and mobile; usage is billed separately, per the same overview. | Step 1, choose how you buy |
| Parent organization | Created automatically when the organization is set up, per Anthropic’s sign-in planning article. | Step 2, owners and domains |
| SCIM | Available for Enterprise and Console organizations only, per Anthropic’s provisioning article. | Step 3, sign-in and provisioning |
| Custom retention | Customers can set custom retention timelines, per Anthropic’s data deletion article. | Step 4, retention and audit visibility |
| Audit logs | Available for Enterprise organizations only, per Anthropic’s audit log article. | Step 4, retention and audit visibility |
Claude for Enterprise: Who Qualifies and Which Route to Take

Qualifying comes down to seats and route. Anthropic’s seat article says Enterprise plans require a minimum of 20 seats, and Anthropic’s plan overview lists two ways in: self-serve, which you purchase directly online without sales involvement, and sales-assisted, where you work with the Sales team. The same overview puts the minimum at 50 seats for the sales-assisted route.
If your headcount sits below the self-serve minimum, this is not your page yet. Anthropic’s Team article says Team plans support up to 150 seats, so Team is the plan to set up first.

For an owner who does qualify, the same overview says the plan includes everything in Team plus additional security and compliance features. The rest of this page is the order I take an owner through.
Step 1: Choose How You Buy
The route is the first real decision because it changes how you pay and who you talk to. According to the plan overview, self-serve usage credits are purchased upfront and billed in USD only, while sales-assisted usage is billed monthly in arrears with multiple currencies supported. The overview also says to contact Sales if you need invoicing, dedicated customer success management or a currency other than USD.
Whichever route you pick, the seat is an access fee only. The same overview says the seat fee doesn’t include any usage, and that the seat gives each user Claude on web, desktop and mobile. Current seat prices are on Anthropic’s pricing page, so I do not repeat them here.
Watch
Budget for access and for usage as two lines. The overview says usage is billed separately from the seat fee, so the seat count alone will never tell you the monthly total.
Three questions settle the route in a few minutes:
- Does the company need invoicing or a currency other than USD? If so, the sales-assisted route is the one to start.
- Would you rather purchase online today without a sales conversation? Then self-serve fits.
- Who signs off on a bill driven by consumption? Name that person before you buy.
Step 2: Set Up the Organization and Its Owners
Anthropic’s sign-in planning article says an Enterprise plan gets a parent organization created automatically when the organization is set up. The same article says a parent organization manages identity and access only: domain verification, sign-in settings and user provisioning. You do not build it, but you do decide who looks after it.

Name the people first. Anthropic’s roles article says an organization can have only one Primary Owner and that the Primary Owner seat uses one of your plan’s licenses. I pick that person for accountability, not convenience, and then write down four things:
- Who is the Primary Owner and stays accountable for access decisions.
- Who else holds Owner or Admin rights, and what each is responsible for.
- Which work email domains belong to the company.
- Who answers billing questions and talks to finance.
Those four answers become one page, and a Claude session can draft it for you in a minute.
Prompt: draft a decision sheet for a claude enterprise setup
Draft a one-page decision sheet for a business owner setting up a company-wide Claude plan. Use six rows: buying route, named owners, company email domains, sign-in method, data retention approach, and who reviews audit logs. For each row, leave a blank answer line and add one question the owner should ask their IT adviser. Do not state any seat count, price, retention period or menu path.
Step 3: Connect Sign-In and Provisioning

Sign-in has an order. Anthropic’s sign-in planning article says domain verification is required before you can configure single sign-on, and Anthropic’s provisioning article assumes single sign-on and domain verification are finished before you set up automatic provisioning. So the sequence is domains, then sign-in, then provisioning. If the first sign-in trips anyone up, my walkthrough of domain capture, SSO and the first login covers each path.
Provisioning comes in two forms. The provisioning article says JIT provisioning is available for Team plans, Enterprise plans and Console organizations, while SCIM provisioning is available for Enterprise and Console organizations only. SCIM is the form that adds and removes accounts from your identity system without anyone logging in first, which is why it matters when staff come and go.
Plan for one interaction. Anthropic’s seat article says users provisioned through JIT or SCIM are assigned a seat when they are added, provided one is available, and that provisioning will not complete until an owner purchases another seat if none is free. Count seats against headcount before you switch provisioning on.
Step 4: Decide Retention and Audit Visibility
These are two separate decisions, and both are Enterprise features. Anthropic’s data deletion article says Enterprise plan customers can set custom retention timelines for their organization’s data, and Anthropic’s audit log article says audit logs are available for Enterprise organizations only. Retention decides how long conversations are kept. Audit logs record who did what.
I settle retention with whoever owns your records policy, because the right answer comes from your obligations and not from the setting. I will not suggest a period here, and be wary of anyone who does before reading your contracts. For what Anthropic keeps by default, my guide on whether Claude keeps your data private is the longer read.
For audit logs, decide who reviews them and how often. The audit log article says Owners and Primary Owners export them, and that the title and content of chats and projects are not in the export, only their unique identifiers. The logs tell you that something happened and who was involved, not what was said.
Step 5: Roll Out to the First Group

With owners, domains, sign-in and the retention and audit decisions in place, the pilot is about habits, not configuration. Start with one group whose work tests the setup honestly:
- Pick a pilot group with everyday work that can test the setup.
- Write a short usage policy covering permitted work and who approves connected tools.
- Invite the group and tell them who to ask for help.
- Review after the first week and adjust before the wider company joins.
Invitations use seats straight away: Anthropic’s members article says pending invitations occupy your available seats immediately, so invite in the order you plan to onboard. Step 2’s decision sheet gives you the names to start from.
Prompt: draft a pilot group usage policy for a claude enterprise plan
Draft a one-page usage policy for a pilot group of about ten employees starting to use Claude at a company. Use plain headings: what Claude may be used for, what company information stays out, who approves connected tools, who staff ask for help, and when the policy is reviewed. Leave every company-specific detail as a blank line for the owner to fill. Do not state any setting, price or retention period.
- Check seats and route first; the minimum differs between self-serve and sales-assisted.
- Name a Primary Owner, a second administrator and the company email domains before anything else.
- Verify domains, then single sign-on, then provisioning, and count seats before turning provisioning on.
- Decide retention and audit-log review with your records owner, not from the setting.
- Pilot with one group, write the usage policy first and review after a week.
If you want a second pair of eyes on the order before you buy, Claude for teams setup on Strategized.ai is where I do that work, and the free Claude guides on Strategized.ai cover the self-paced side. The next step is a conversation about your owners, sign-in and rollout, not a purchase. Everything else I have written for owners is in my tested Claude strategies.
Frequently Asked Questions
Can I buy a Claude Enterprise account without talking to sales?
Yes, if you meet the seat minimum. CoworkStrategy.com reads Anthropic’s plan overview, which says the self-serve route is purchased directly online without sales involvement.
What comes first after buying Claude for Enterprise?
Name your owners and verify your email domains. CoworkStrategy.com follows Anthropic’s sign-in planning article: the parent organization is created automatically, and domain verification comes before single sign-on.
Does a Claude Enterprise plan include SCIM when Team does not?
Yes, SCIM is for Enterprise and Console organizations only. CoworkStrategy.com reads this from Anthropic’s provisioning article, which adds that JIT provisioning is available on Team too.
Can an owner set custom data retention on a Claude Enterprise plan?
Yes. CoworkStrategy.com cites Anthropic’s data deletion article: Enterprise plan customers can set custom retention timelines for their organization’s data. The period is a records-policy call.
Does the Claude for Enterprise seat fee include usage?
No. CoworkStrategy.com points owners to Anthropic’s plan overview, which says the seat fee covers access only and usage is billed separately.
Can a Team plan organization upgrade to a Claude Enterprise account?
Yes. CoworkStrategy.com notes that Anthropic’s plan overview describes organizations upgrading from a Team plan to self-serve Enterprise. Check your seat count against the minimum first.



