How to Set Up Claude for Teams: A Complete Guide

Most teams that buy Claude Team seats waste the first month. They hand out logins, run a lunch-and-learn, and watch adoption quietly die.

The account setup takes 90 minutes. The part that decides whether it was worth the money takes deliberate effort.

This guide covers both: the account mechanics in the right order, and the four things that separate teams actually running on Claude from teams that just have access.

Key takeaways

• Two jobs, one guide: Account setup takes an afternoon; real adoption takes four deliberate steps after that.
• Standard vs. Premium seats matter: Standard seats cover most business users at $20/seat/month; Premium at $100/seat/month is for heavy daily users who would hit rate limits on Standard.
• Projects are the most important feature most teams skip: A shared Project gives every team member the same context, voice, and instructions from session one.
• Data protection is default on Team plans: Anthropic does not train on your content by default; no configuration required.
• SSO and domain capture matter at 20+ seats: Set these up before inviting the full team, not after.
• One workflow before broad rollout: Pick one high-friction recurring task, run it in Claude, prove it works, then expand.

What is the Claude Team plan?

The Claude Team plan is Anthropic’s multi-user subscription for groups of 5 to 150 people.

It provides shared AI access with centralized billing, admin controls, and data protection that individual plans do not offer.

Every seat includes access to all available Claude models, a 200K token context window, priority access during peak periods, and access to Claude Code, Claude Cowork, and Claude Design.

• Standard seats: $20/seat/month on annual billing or $25/seat/month on monthly billing; covers most business users.
• Premium seats: $100/seat/month on annual billing or $125/seat/month on monthly billing; for power users who need significantly higher usage capacity.
• Mixed seat types: You can assign Standard and Premium seats within the same organization; not everyone needs the same tier.
• Minimum size: 2 seats to create a Team plan; 5 seats is the practical minimum before the admin overhead makes sense.
• Maximum size: 150 members; above that, Enterprise is the appropriate plan.

The key difference from individual Pro plans is not just usage.

It is the organizational controls: centralized billing, domain verification, SSO, role-based permissions, and spend caps that let one admin manage the whole team.

What do you need before you start?

Account setup is faster when three things are confirmed before you touch the billing screen.

• A work email domain: Claude Team uses domain-based membership. Everyone who joins needs an email address on your organization’s approved domain; personal Gmail addresses create management problems later.
• A designated Primary Owner: One person controls billing, seat allocation, and organizational settings. Decide this before signup; changing it later requires a support request.
• A rough seat count and type split: Decide how many Standard and how many Premium seats you need before purchase; seat type upgrades are prorated and immediate, but over-buying Premium seats from the start is a common and expensive mistake.

If your team is already on individual Pro or Max plans, you can migrate those accounts into the Team organization after creation; covered in the migration section below.

How to create a Claude Team account

Account creation is a linear flow. The steps below are in order; do not skip the domain verification step even if it feels optional.

Step 1: Create the organization

Go to claude.ai/login with your work email. Follow the onboarding prompts and select the Team plan.

If you already have an individual Claude account on the same email, sign in first and then visit claude.ai/upgrade; upgrading creates a new organization separate from your personal account.

Choose annual billing if your team size is stable; the per-seat cost is 20% lower than monthly.

Choose monthly billing if you are still figuring out how many seats you need.

Step 2: Purchase and assign seats

After organization creation, navigate to Organization settings > Billing. Set your total seat count and choose the split between Standard and Premium.

The most common mistake here is buying all Premium seats because it feels safer. Standard seats cover all Claude features for most business users.

Reserve Premium for team members who will use Claude for multiple hours of daily work and would otherwise hit rate limits.

A realistic split for a 10-person team is 7 Standard and 3 Premium.

• Standard seat: All Claude models, Claude Code, Claude Cowork, Claude Design, connectors, enterprise search.
• Premium seat: Everything in Standard plus significantly higher usage limits; for daily heavy users.
• Seat reassignment: Admins can upgrade or downgrade seat types in Organization settings > Members without purchasing new seats if allocation exists.

Step 3: Verify your domain

Navigate to Organization settings and add your company domain. Claude will generate a DNS TXT record.

Add that record to your domain’s DNS settings and verify it.

Domain verification unlocks two features: domain capture and SSO.

Domain capture lets colleagues with a matching email address find and request to join your organization automatically.

SSO integrates with SAML-based providers like Okta or Azure AD. Both are significantly harder to configure after the team is already onboarded.

Step 4: Invite your first members

With domain verified and seats purchased, go to Organization settings > Members and click Add member. Enter each person’s work email.

They will receive an invite and be assigned to the available seat type.

For teams of 20 or more, configure Just-in-Time (JIT) provisioning or SCIM before sending individual invites.

This lets new hires get Claude access automatically when their identity provider account is created, rather than requiring a manual invite for each person.

Step 5: Set organization-level instructions

Before anyone starts using Claude in your organization, set organization instructions.

These are persistent system-level instructions that apply to every Claude session across your team; the closest thing to a company-wide prompt.

Use organization instructions to encode your company name, industry, and tone of voice.

Also specify what Claude should never include in outputs, such as client names in examples or competitor mentions, and what format your team’s outputs typically follow.

This step takes 20 minutes and prevents the most common team Claude complaint: “everyone gets different outputs.”

How to connect your tools

The Claude Team plan includes connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365, and Slack.

Enterprise search pulls answers from across all connected tools in one place.

Connectors are configured per user, not organization-wide; each team member connects their own accounts.

The admin’s job is to enable or restrict which connectors are permitted through Organization settings > Plugins.

• Google Workspace connector: Connects Gmail, Google Drive, and Google Calendar; most useful for teams whose core work lives in Google Docs and Sheets.
• Microsoft 365 connector: Connects Outlook, OneDrive, and SharePoint; as of July 2026, Teams integration is read-only only.
• Slack connector: Gives Claude context from Slack conversations; useful for briefing Claude on ongoing projects without copy-pasting.
• GitHub connector: For engineering teams; connects repositories and issues.

Connect the two or three tools your team uses most before asking anyone to start working in Claude.

Context from connected tools is what makes Claude outputs feel specific to your business rather than generic.

How to set up shared Projects

Projects are the most important feature most teams skip during setup.

A shared Project holds all the context, documents, and instructions for a body of work in one place.

Without Projects, every team member builds their own context from scratch in each session. With Projects, they all start from the same setup.

What to put in every shared Project

Each Project has a knowledge base (uploaded documents) and a system prompt (instructions that apply to every conversation in that Project).

The knowledge base should contain: your brand voice guide, relevant process documents, any recurring templates or formats the team uses, and background documents on the clients or topics that Project covers.

The system prompt should specify what role Claude is playing in this Project and what format outputs should follow.

Also include what this team cares about that generic Claude would not know, and any constraints specific to your standards.

Which Projects to create first

Do not try to build Projects for every workflow on day one. Create Projects for the three recurring tasks your team produces most often.

Common starting points:

• Content and copy: Brand voice guide, style sheet, example outputs; anyone who writes for the company uses this Project.
• Client communications: Client brief, past communications, tone guidance; outputs feel like they come from one person.
• Internal reporting: Report templates, key metrics definitions, formatting rules; consistent outputs without back-and-forth on format.

Build one Project, use it for two weeks, then build the next one.

Teams that build five Projects on day one use none of them by week three.

How to migrate existing individual accounts

If team members already have Claude Pro or Max accounts on their work email, those accounts need to be claimed and migrated into the Team organization.

Navigate to Organization settings and look for domain claim options.

Accounts on your verified domain that are not yet part of your organization will appear for claiming.

The Primary Owner initiates the migration; affected users will be notified and their existing projects and history will transfer into the organizational account.

Individual billing stops for migrated accounts; the organization’s Team plan covers them from the migration date.

Tell affected team members before initiating the claim; unexpected account changes create friction on rollout day.

What to do in the first two weeks after setup

Account setup is done. This is where most deployments either compound or quietly stall.

Week one: one workflow, one team, real work

Pick one team and one recurring task.

Do not pick the most complex workflow; pick the one with the highest volume of manual effort and the most consistent output format.

Brief that team on the relevant Project, run the workflow in Claude, and review the outputs together.

The goal is one “this is faster and better than what we were doing” moment inside the first five working days.

That moment is what drives the rest of adoption; no lunch-and-learn produces it.

Week two: identify what the Project is missing

After a week of real use, the Project’s knowledge base will have visible gaps.

Team members will have added context manually in conversations that should have been in the Project to begin with.

Update the knowledge base and system prompt based on what you observed.

This is a one-hour session with whoever used Claude most that week.

The output is a Project that produces noticeably better first drafts than it did on day one.

The compounding starts here, not at account creation.

Common setup mistakes and how to avoid them

Most Claude Team deployments that stall make the same errors.

• Buying all Premium seats: Most business users do not hit Standard rate limits in normal daily use; over-buying Premium adds 5x cost per seat for usage you are not consuming.
• Skipping domain verification: You can configure it later, but SSO and automatic member discovery both depend on it; configure it on day one.
• No organization instructions: Every team member gets generic Claude without them; the outputs feel inconsistent and people conclude Claude does not know their business.
• Building too many Projects at once: Five empty Projects with no knowledge base are worse than one well-built Project; start with one, prove it, then expand.
• Skipping the migration step: Individual accounts still paying separately for Pro or Max while on a Team plan are a billing and permissions problem; claim and migrate them before rollout.

Conclusion

Setting up Claude Team takes 90 minutes if you do the steps in order.

Create the organization, purchase the right seat mix, verify your domain, set organization instructions, and build one shared Project before inviting the full team.

The part that decides whether the investment compounds is what happens in week one.

Pick one real workflow, run it with a real team, and update the Project based on what you learn.

That loop, repeated over time, is how teams go from having Claude access to running their operations on it.

Want your team to actually run on Claude, not just have access to it?

Getting the Team plan live is the straightforward part.

Building the Projects, training each function on their specific workflows, and designing the operations that produce compounding output is where most teams need a partner who has already done it.

Phos AI Labs is an AI implementation firm for small and mid-market businesses.

We set up Claude Team organizations and build the Projects and context systems that make every team member’s outputs consistent.

We train your team inside their real workflows and stay until Claude is how the business runs.

• AI Foundations first: Before training anyone, we build the operating documents and context packs that make every Claude session more accurate and more specific to your business.
• Team training that sticks: We train each function on the workflows they actually do, not on generic AI prompting theory.
• Private AI Workspace: We build the Projects, shared context, and organization instructions that make Claude feel like it knows your business from day one.
• AI Implementation: We redesign the recurring work that costs your team the most time, until Claude is part of how the work gets done, not an experiment.
• Strategy before systems: We identify which workflows to build first and which to leave alone before touching any configuration.
• Honest judgment: We tell you what a Team plan can do and what requires a deeper implementation to produce real results.
• We stay until it works: Our engagements are measured by whether the team actually uses Claude in their daily work, not by the number of seats activated.

400+ engagements. Clients include Zapier, Coca-Cola, Medtronic, Dataiku, and American Express.

Start the conversation at Phos AI Labs when you are ready to go further than account setup.

FAQs

What is the minimum team size for a Claude Team plan?

The minimum is 2 seats to create a Team plan, though 5 seats is the practical threshold where the admin overhead and pricing make more sense than managing individual Pro subscriptions.

Can I mix Standard and Premium seats on the same Claude Team plan?

Yes. You can assign different seat types to different team members within the same organization.

Admins can upgrade or downgrade individual members between Standard and Premium in Organization settings > Members without purchasing new seats if the allocation exists.

Does Claude train on my team’s data?

No. Anthropic does not train on customer content by default on Team and Enterprise plans.

You do not need to configure anything to enable this; it is the default behavior.

What happens to individual Pro accounts when I set up a Team plan?

They continue billing separately until you claim and migrate them into your Team organization.

Use the domain claim feature in Organization settings to identify accounts on your verified domain and migrate them.

Individual billing stops for migrated accounts from the migration date.

Do I need SSO to set up a Claude Team plan?

No. SSO is optional on the Team plan.

It is worth configuring if your organization already uses a SAML-based identity provider like Okta or Azure AD, because it simplifies member management at scale.

It requires domain verification first.

What is the difference between a Project and organization instructions?

Organization instructions apply to every Claude session across your entire team, regardless of which Project they are in.

A Project’s system prompt applies only to conversations within that Project. Use organization instructions for company-wide rules; use Project instructions for workflow-specific context.