How to Set Up Claude for a Team.

A plain walkthrough for a small firm: pick the right plan and seats, protect the data, invite the people, and turn Claude into a tool the team actually uses — not a tab everyone forgets about by Friday.

The Short Version

Setting up Claude for a team is two jobs that get confused for one. The first job is the account: choosing the plan, buying seats, inviting people, and making sure the firm data is handled correctly. That part takes an afternoon. The second job is the one that decides whether the money was worth it: getting the team to use Claude for real work, every day, on the tasks that fill the week. That part takes longer and is where most of the value lives.

This guide covers both, in order. Start with the plan, settle the data question, get one workflow working, then build from there. If you have not settled which plan yet, the Claude Team plan explained covers the seats, the billing, and the admin roles before you buy. The implementation roadmap lays out the week-by-week sequence, and this page — one guide in the broader Claude Implementation hub — covers the setup decisions you make first.

If you want this done with you

The steps above are enough if you want to run the setup yourself. Plenty of firms do.

If you want it done on your account, that is a conversation. I stand AI up in the firm — on the tool you searched or on what the firm should run next. One session covers the plan, the first project, and one real workflow on your work.

Call or text 904-233-6290  ·  Or use the form →

Tell me the one task that eats your week — I’ll show you what Claude does with it, free. Show me on my work →

Step 1 Plan and seats Step 2 Settle data Step 3 Invite team Step 4 One workflow Step 5 SKILLS, CONNECTORS Step 1 · Plan and seats Step 2 · Settle the data Step 3 · Invite the team Step 4 · One workflow Step 5 SKILLS, CONNECTORS

The order this page walks through — account first, then the one workflow, then the skills and connectors that make it stick.

Step 1 — Pick the Plan and the Seats

For a team, this is the Claude Team plan. Here is what it costs and how the seats work.

Team Standard. 25 dollars per seat per month, or 20 dollars per seat billed annually. This is the default seat for everyone — writing, analysis, research, shared projects, more usage than the individual Pro plan, plus the team-level admin and billing controls.

Team Premium. 125 dollars per seat per month, or 100 dollars annually. Much higher usage per seat, plus Claude Code for anyone doing heavier or technical work. You only put your heavy users on Premium.

The minimum and the mix. The Team plan requires at least two seats and runs up to 150 people. You can mix Standard and Premium in the same workspace, so a typical small firm puts everyone on Standard and upgrades only the one or two people who keep hitting limits. Seat types can be changed later, so there is no need to over-buy on day one.

Step 2 — Settle the Data Question

This is the step a consumer-plan setup skips, and it is the one that matters most for any firm handling client information. On the Team plan, business conversations are not used to train models by default, and administrators control how data is handled. That is the line between a setup that is safe for confidential client work and one that is not.

The free and Pro consumer plans are fine for trying Claude on material that is not sensitive. They are not the place for client files. For law firms specifically, the February 2026 federal ruling on AI and attorney-client privilege made the plan choice a real decision. The small law firms guide covers that ruling and what it means for which plan a firm should be on. The confidentiality guidance for lawyers is the page on client information.

Step 3 — Invite the Team and Set Up Shared Projects

With the plan chosen, an administrator invites people, assigns seat types, and sets up the workspace. The piece worth doing here rather than later is shared projects — a project holds the context, files, and instructions for a body of work in one place, so the whole team starts from the same setup instead of each person building their own from scratch. A project per client, per matter, or per recurring task is the common pattern. This is the foundation the skills and connectors plug into next.

Two ways to add people. There are two ways to get someone into a Claude Team workspace: an email invitation sent from the workspace, or a shareable invite link that anyone can open to join on their own. The email route gives whoever sends it control over the seat type and the role each person lands on. The link route is faster for a group, because people join themselves instead of waiting for an invitation to be issued one at a time. On Team plans ordinary members can send email invitations too, not only administrators, and an administrator can require approval for those.

Sending an email invitation. Open Organization settings, then Members, and click Add member. Enter the email address — it has to match one of the domains the organization allows — choose the seat type, set the role, then click Add members. The invitation email stays valid for 21 days. To bring in several people at once, Bulk add takes a list of addresses separated by commas or line breaks.

Using the invite link. The invite link lives in Organization settings under Organization and access, and it is switched on by default for Team plans. It expires automatically 90 days after it is created, and an administrator can disable or regenerate it at any time. Anyone who joins through the link is added automatically at the lowest available seat tier, with no separate approval step, so it is the right tool for a known group and the wrong one for a link that might travel.

What the person on the other end needs. Nothing in advance. They do not need an existing Claude account — opening the invitation prompts them to sign up or log in, and their email domain is then checked against the ones the organization allows. One thing worth knowing before sending a batch: a pending invitation takes up a seat the moment it goes out, not when it is accepted, so unaccepted invitations count against the seats already bought.

Removing someone. In the Members list, the menu beside a person’s name has Remove from team. Access ends immediately and the seat becomes available to assign to someone else, though freeing a seat does not by itself lower the bill.

Step 4 — Get One Workflow Working

Resist the urge to turn on everything. Pick the single task the team does most often that follows a pattern — a first-draft client letter, an intake summary, a weekly report — and set Claude up to do it well from start to finish. One workflow that the team uses every day beats ten features nobody remembers. The first visible win is what builds the habit that carries the rest of the rollout.

If you want this done with you

The steps on this page are enough if you want to run the setup yourself. Plenty of firms do.

If you want it done on your account, that is a conversation. I stand AI up in the firm — on the tool you searched or on what the firm should run next. One session covers the plan, the first project, and one real workflow on your work.

Call or text 904-233-6290  ·  Or use the form →

Step 5 — Add Skills, Then Connectors

This is what moves a team from casual use to operational use.

Skills first. A skill teaches Claude how the firm works once, in a form it reads every time — the voice, the processes, the common tasks, the rules. With a skill behind the first workflow, every conversation starts ahead of where the last one ended instead of re-explaining the firm each time. The skills guide covers what to put in your first three.

Connectors next. A connector lets Claude reach the email, calendar, files, or system the firm already runs, so it can read the actual file instead of waiting for someone to paste it in. Wire the safe, high-value ones first and leave the rest. The connector guide covers which ones small firms actually use.

Who completes the initial setup for enterprise search?

An Owner or Primary Owner does. Enterprise search — the “Ask Your Org” project — is enabled by default on Team and Enterprise plans, and it appears in every member’s sidebar from day one. That is what trips teams up: it looks ready, and it is not. Until an Owner opens the project, clicks Set up for your org, and connects at least one documents source and one chat source, members can see the project and get nothing from it.

Admins cannot complete this step. Members cannot either. It is Owner-only, which means whoever holds the Owner role in your workspace is the one person who can turn a visible-but-empty project into a working one. On a small firm’s Team plan, that is usually the person who created the workspace.

The setup itself takes minutes. The decisions around it — which connectors to allow, what data they can reach, who pilots it first — take longer and matter more. The full walkthrough, including connector order and permissions, is on the Claude enterprise search setup page.

What This Setup Will Not Do

Worth being plain about.

It will not adopt itself. Buying seats is not adoption. A team that gets accounts but no workflow, no skill, and no training goes back to the way it worked before inside a month. The setup is the start, not the finish.

It will not make the judgment. Claude does the first pass — the draft, the summary, the prep. The professional still owns the output and the responsibility. The time saved is the blank-page time, not the judgment.

It will not stay current on its own. Claude ships new features constantly and the firm changes too. A short quarterly review keeps the seats, skills, and workflows aligned. Skip it and the setup drifts.

Every step on this page is yours to run, and the guide is the whole method — plenty of firms work through it in an afternoon and never call anyone. Where I come in is that last point: Claude Implementation is a managed service, so the setup gets built and then kept current month to month as Claude changes. Ask what that looks like →

Frequently Asked Questions

What plan do I need to set up Claude for a team?

The Claude Team plan. It adds the things a group needs that the individual Pro plan does not: central billing, admin controls, shared projects, and business data protection by default. Team has two seat types you can mix in one workspace. Standard seats are 25 dollars per seat per month, or 20 dollars billed annually, and cover everyday writing, analysis, and research. Premium seats are 125 dollars per seat per month, or 100 dollars annually, and add much higher usage plus Claude Code for anyone doing heavier work. The plan requires a minimum of two seats and scales to 150 people before Enterprise becomes the better fit.

How many seats do I have to buy?

At least two. The Team plan requires a minimum of two seats and supports up to 150. Billing follows the seats on the plan rather than how many are in use — removing a member frees that seat for someone else but does not lower the bill, so the two-seat minimum is what a firm pays even if only one person is using Claude. Most small firms start everyone on Standard seats, watch usage for a few weeks, and upgrade only the one or two heavy users to Premium. You do not have to guess up front, because seat types can be changed later and take effect on the next billing cycle.

How do I invite someone to Claude?

On a Team plan, an administrator opens Organization settings, then Members, clicks Add member, enters the email address, picks the seat type and the role, and clicks Add members. That sends an invitation email which stays valid for 21 days, and Bulk add takes a whole list of addresses separated by commas or line breaks. The faster route for a group is the invite link, found in Organization settings under Organization and access, which is switched on by default for Team plans and expires automatically 90 days after it is created. On Team plans ordinary members can invite teammates by email as well, not just administrators, and an administrator can require approval for those invitations.

How do I join a Claude team someone invited me to?

Open the invitation email or the invite link you were sent, then sign up or log in. You do not need an existing Claude account first: the link prompts you to create one or sign in, then checks your email domain against the domains the organization allows. If the domain matches you are added to the organization automatically, with no approval step, at the lowest available seat tier. If it does not match, or the workspace has already used every seat it bought, you get an error instead and the workspace administrator has to resolve it.

Is our data safe on the Claude Team plan?

On the Team plan, your conversations are not used to train models by default, and administrators control how data is handled. That is the main reason any firm doing real client work should be on Team or above rather than a consumer plan. The free and Pro consumer plans are fine for testing on material that is not sensitive, but they are not the place for confidential client information. For law firms, the February 2026 federal ruling on AI and attorney-client privilege turned the plan choice into a real decision rather than a detail.

What is the first thing to do after the team is set up?

Pick one task the team does often and set Claude up to do it well, end to end. A first-draft client letter, an intake summary, a weekly report. Getting one workflow working and used beats turning on every feature and having the team forget about it in a week. The first visible win is what makes the rest of the rollout stick.

Do we need skills and connectors right away?

Not on day one, but soon. A team can get value the first week just from shared projects and good prompts. Skills, which teach Claude how the firm works once, and connectors, which let Claude reach the email and files the firm already runs, are what move the team from casual use to operational use. Most setups add the first skill within the first month and the first connector shortly after.

Can different people on the team have different access?

Yes. Administrators control who is on the workspace, who has Standard versus Premium seats, and how billing is handled centrally. For tighter control of connectors and audit needs, Enterprise adds the deeper administration features compliance teams ask for. Most small firms do not need that level, but it is there when a firm grows into it.

How long does it take to set up Claude for a small team?

The account, seats, and invitations take an afternoon. Getting the team actually using Claude for real work is the part that takes longer, and it is the part that matters. The order that works is one good workflow live first, then the first skill and connector, then a few core workflows running. The roadmap guide lays out that sequence.

Should we set this up ourselves or get help?

Buying seats and inviting people is simple and most firms handle it themselves. The work that takes outside help is the part after that: authoring the skills that teach Claude the firm, wiring the connectors safely, and training the team so the tools become habits. A firm comfortable with that can do it alone. A firm that wants it working sooner usually brings in help for the setup, then runs it itself. See consulting vs doing it yourself for how to tell which side of the line you are on.

Related Guides

Other pages inside the Claude Implementation hub that connect to this one.

Call Contact