Claude Team Plan: What You Get and a 7-Day Rollout

When a business owner tells me they've got three or four people all using Claude on their own personal accounts, I know what's coming next. Nobody can see anyone else's work, everyone has written their own instructions from scratch, and the one person who set it up well can't share what they've built. That's the problem the Claude Team plan is designed to fix.

Here's what the Team plan includes according to Anthropic, who it suits, and the week-long rollout I'd follow so your team gets value from it straight away rather than treating it as another login.

What is the Claude Team plan?

The Team plan is Anthropic's plan for using Claude as a group. Anthropic describes it as built for teams, and it sits between the individual plans and Enterprise. It needs a minimum of two members and supports up to 150 seats. If you grow beyond that, the next step up is the Enterprise plan.

The key difference from everyone having their own account is that the business owns the workspace. You manage who has access from one place, you can share projects between colleagues, and an owner controls settings such as memory and which features are switched on.

What's included in the Claude Team plan?

Anthropic lists these for Standard seats on the Team plan:

• More usage per session than the individual Pro plan.
• Admin tools to manage access in one central place.
• Identity and access controls: single sign-on and domain capture, just-in-time provisioning and role-based permissions.
• Enterprise search: a dedicated search project that can search across Slack, Microsoft 365 and custom connectors.
• Connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack, so Claude can find context in your existing documents, email, calendars and team chat without manual uploads.
• Everything in Pro, including all available models, Claude Code, Cowork, projects, knowledge bases and collaboration features.

There are two seat types. Standard seats suit most people. Premium seats give significantly more usage, and Anthropic says you can mix and match, so your heaviest users get Premium seats while everyone else stays on Standard.

Do Claude Team plan usage limits apply to the whole team?

No, and this matters more than people expect. Anthropic says usage limits on the Team plan are per member, not shared across the team. Each person has their own limits, and if one member reaches theirs, everyone else carries on as normal. Weekly limits reset at a fixed time each week, and each person can see their next reset time in Settings, Usage.

In practice, that means one enthusiastic colleague can't use up the whole team's allowance, which is one of the most common worries I hear before a rollout.

How do shared projects work on the Team plan?

Shared projects are the feature that makes the Team plan worth setting up well. A project holds its own documents, instructions and chat history. On Team and Enterprise plans, you can share a project with specific colleagues, by email or in bulk, or make it available to the whole organisation.

Each person gets one of two permission levels:

• Can view: they can see the project's contents, knowledge and instructions and chat within it, but can't edit it.
• Can edit: they can change the instructions and knowledge, add or remove members and contribute fully.

Owners can turn project sharing off for the organisation if they want to keep things locked down. If you're new to projects, my guide to setting up Claude Projects walks through the basics.

Who controls memory on the Team plan?

On Team and Enterprise plans, owners decide whether memory is available, and it's switched off for each member until they turn it on. That's a sensible default for a business: nobody's personal preferences leak into shared work by accident, and you can decide as a team whether you want it.

Is the Claude Team plan worth it for a small business?

I'd look at it once two or more people are using Claude for work every week. The signs it's time:

• People are rewriting the same instructions and prompts on separate accounts.
• Client or company documents are being uploaded to personal accounts you don't control.
• You want to switch features such as memory or web search on or off for everyone at once.
• Someone has built a brilliant project and nobody else can use it.

If it's just you, an individual plan is simpler. If you've got a handful of people and no shared way of working, the Team plan gives you the structure, but only if you spend the first week setting it up.

What should go in your team's AI house rules?

Before anyone starts, agree a short set of rules and pin them where everyone can see them. Keep it to one page. I'd cover what can never be pasted in, such as passwords and anything under a confidentiality agreement; which projects people should use for which jobs; who checks AI-drafted work before it reaches a client; and who to ask when something looks wrong. It sounds formal for a small team, but it's what stops one person's shortcut becoming everyone's problem.

A seven-day Claude Team plan rollout

This is the rollout I'd use with a team of three to ten people.

1. Day one: the owner sets up the workspace, decides on seat types and invites everyone.
2. Day two: agree the house rules: what can and can't be pasted in, and which connectors to switch on.
3. Day three: build one shared project per big job, such as client proposals or customer replies, with the key documents and instructions inside.
4. Day four: each person brings one real weekly task and runs it inside the right project.
5. Day five: compare results, fix the instructions that produced weak drafts and decide on memory.
6. Day six: write a short how-we-use-Claude page and pin it.
7. Day seven: pick one recurring job to hand to Cowork and agree who checks its work.

Here's the prompt I'd use on day three to write the instructions for each shared project.

Copy this prompt

We're a [type of business] with [number] people. I'm setting up a shared Claude project for [job, for example client proposals].
Write project instructions that cover: who we are, who the work is for, our tone of voice, words we never use, the format we want, and what Claude should always ask us before it starts.
Keep it under one page and write it so a new team member could follow it.

And one for day five, to tighten the instructions after a week of real use:

Copy and paste this prompt

Here are our project instructions: [paste them].
Here are two drafts the team wasn't happy with and what was wrong: [paste them].
Rewrite the instructions so these problems don't happen again. Show me only the lines you changed.

Tools that work well alongside it

Most teams get the most from the Team plan when it's connected to where their work already lives: Google Drive, Gmail and Google Calendar, or Microsoft 365, plus Slack for team chat. Keep one shared document of approved prompts in whichever of those you use, so new starters can find them.

If you'd like the rollout done with your team rather than worked out alone, this is how I help business owners set up AI tools that people use.

Frequently asked questions

What is the Claude Team plan?

It's Anthropic's plan for using Claude as a group. It needs at least two members, supports up to 150 seats, and adds central admin, shared projects, connectors and identity controls on top of everything in Pro.

Are Claude Team plan limits shared across the team?

No. Anthropic says usage limits are per member. If one person reaches their limit, everyone else can keep working.

What's the difference between Standard and Premium seats?

Premium seats give significantly more usage than Standard seats. You can mix both in one team, giving Premium seats to your heaviest users.

Can you share projects on the Claude Team plan?

Yes. You can share a project with specific colleagues or the whole organisation, with Can view or Can edit permissions. Owners can turn project sharing off.

Is memory on by default on the Claude Team plan?

No. On Team and Enterprise plans, owners control whether memory is available, and it's off for each member until they turn it on.