Home › Blog › From One Claude User to a Team: An Owner’s Checklist

From One Claude User to a Team: An Owner’s Checklist

Short answer

Claude team setup is the order an owner follows to go from one person using Claude to a small team using it the same way: decide who gets a seat, write down the work and the rules, then invite people. I take owners through it at CoworkConsultant.com, one decision at a time.

If you are the only person in your business who uses Claude, you already know what works. Your colleagues do not, and the gap shows up the day you invite them. This checklist is the order I follow with owners so that the first invitation goes out after the decisions are made, not before.

Question Short answer
What to write down first The one repeatable job you want handled and what a good result looks like
Who gets a seat The person accountable for that job, then the colleagues who do it every week
Which connectors Only the ones the first job needs, approved by one named person
What it never does It does not replace your judgment, certify a tool or promise a result

Claude Team Setup: What Changes When a Second Person Joins

Two dental front desk staff reviewing a handoff at the reception desk - a guide to claude team setup
The handoff starts at the desk where the work already happens.

Adding a colleague changes the job. Anthropic’s help article on the plan says Team plans require a minimum of two members and support up to 150 seats, and that usage limits are per member, not applied to the team as a whole. So your habits stop being the only ones that matter, and every person works inside the same organization.

The page also describes shared features for projects, knowledge bases and collaboration, plus central billing and access. Those are tools. They do not decide what your team should use Claude for, who checks the output or what stays out. Those decisions belong to you, and they are the part I help owners make.

The Owner Checklist From One Account to a Team

Five step owner checklist flow from seat decisions to invitations - a guide to claude team setup
The order I follow: decisions and a written brief first, invitations last.

Work through these in order. Each step is cheap before invitations go out and expensive after.

  1. Decide who gets a seat first. Start with the person who owns a recurring job and can judge the result.
  2. Write down the job. Name one repeatable task and what a good result looks like.
  3. Set the usage rules. Say what never goes into Claude, who reviews important output and which decisions stay with a person.
  4. Choose connectors. List the tools the job needs and name one person who approves access.
  5. Decide how you upgrade your own account. Settle whether your personal chats move into the business.
  6. Invite people in small batches. Confirm which work email domains your organization allows first.
  7. Run a first week check. Review real examples with the team and correct unclear guidance.

A month in, decide which jobs to keep, revise or add, based on the work people actually did and how good it was.

Upgrading Your Own Account Without Losing Your Chats

If you already use Claude on a work email, you will probably upgrade the account you have. Anthropic’s getting started article says to sign in, visit claude.ai/upgrade and follow the steps to create your Team. It adds that the person creating the account must use a business email address.

One checkbox matters. The same article says that if you see the Keep your personal account separate checkbox, upgrading by default upgrades your existing organization in place and some of your content carries over. It also says that once content has been moved into an organization, it cannot be moved back to a personal account. I ask owners to decide that before clicking, because personal conversations and business work rarely belong together.

Your colleagues face a milder version of the same question. Anthropic’s member management article says someone who already uses Claude personally with a work email can join your team and will then have both a personal account and a team account, and can switch between them from the menu.

Watch for

Do the personal versus business decision on your own account before you invite anyone. A rule you make after colleagues have joined is a rule they have already worked around.

Who Gets a Seat First

A paralegal at a desk beside shelves of binders working on a shared team workflow - a guide to claude team plan
One person owns the workflow before anyone else is invited.

Begin with the person accountable for the job and the colleagues who perform it repeatedly. Choose work where someone can judge the result against a clear standard. Giving access broadly before anyone agrees how the output will be used leaves each person to invent a process.

  • Count yourself.Anthropic’s roles article says an organization can only have one Primary Owner and that the Primary Owner seat uses one of your plan’s licenses.
  • Invitations take seats. The member management article says pending invitations occupy your available seats immediately, and that an invitation expires after 21 days. Send them in small batches so a seat is not tied up by an invitation nobody has answered.
  • Domains matter. The same article says an invited person’s email must use one of your organization’s allowed email domains.
  • Seat types can differ.Anthropic’s seat article says organizations can mix and match seat types, and describes the higher tier as everything in the standard seat plus higher usage limits. Current prices are on Anthropic’s pricing page, and I do not quote them here because they change.

What to Write Down Before You Invite Anyone

One page brief hub with the task roles rules sources and connectors - a guide to claude team account
Five things on one page, written before the first invitation goes out.

A one page brief gives colleagues a shared reference and gives me something concrete to build around. It needs five things.

  • The repeatable task Claude should help with, and what a useful result looks like.
  • The roles involved, who owns the process and who approves the final work.
  • The rules: what never goes into Claude, tone, and quality standards.
  • The sources Claude may use, with sensitive material clearly marked.
  • The connectors the job needs and the person who signs off on access.

Two prompts help you get there. Each works in a fresh Claude session with nothing attached, because each asks for a document and never touches a real person’s information.

Prompt: draft a one page brief for a claude team plan

Draft a one page brief for a small business owner who is about to invite colleagues to Claude. Use these headings: the one repeatable job, what a good result looks like, who owns it, who approves the output, what must never be typed into Claude, and which tools the job needs. Write in plain sentences. Where the owner must decide something, write DECISION NEEDED in capitals and name the choice. Do not invent policies, settings or prices.

You get a first draft with decision markers. Settle each marker yourself and keep the page short enough that a new colleague reads it in two minutes.

Prompt: build a first week review checklist for a claude team account

Write a one page first week review checklist for a small business owner who has just invited three colleagues to Claude. Include five questions to ask each colleague, three things to look for in the work they produced, and a simple way to record corrections to the written guidance. Use plain language and keep it to one page. Do not invent policies, settings or prices.

You get a checklist to run on day five. Use it with real examples of everyday work, and treat every correction as a change to the brief, not a fault in the person.

Which Connectors to Turn On, and Who Decides

Three colleagues around one monitor with one pointing at the screen - a guide to claude team account
Colleagues learn the shared setup on a real task, together.

Connectors decide what Claude can reach, so one person should approve them. Anthropic’s Google connectors article says that on Team and Enterprise plans an Owner or Primary Owner must enable those connectors at the organization level before individual users can authenticate. Anthropic’s pricing page also lists admin controls for remote and local connectors among the shared features.

My advice is to enable only what the first job needs. Anthropic’s article on the plan names Google Drive, Gmail, Google Calendar, Microsoft 365 and Slack among the connectors available, but a longer list is not a reason to turn them all on. Every extra connector is one more thing someone has to approve and explain.

Tip

Write the connector approver’s name on the one page brief. When a colleague asks for access to another tool, they already know whom to ask, and you are not the bottleneck.

Where Owners Go Wrong

  • Inviting people before agreeing on the work. Access without a shared purpose leaves each person to invent a different process.
  • Assuming your own habits will carry over. Colleagues need guidance that reflects their roles and standards, not a copy of how you work.
  • Sharing too much reference material. Outdated or irrelevant files make focused work harder and can reach people who should not see them.
  • Skipping human review. Claude can help produce work, but someone still checks important output and owns consequential decisions.

What This Never Does

A contractor and a colleague at a laptop beside rolled plans in a site office - a guide to claude team setup
Everyday desk work is where a team brief earns its keep.

A written brief does not make a tool compliant, certify any setting or guarantee a result. It does not replace your own privacy and security review, and it cannot settle requirements that depend on your industry. I do not promise outcomes from a setup. I help you make the decisions in order and write them down so your team can follow them.

It also does not decide for you. Which jobs to hand to Claude, which to keep with a person and what to do when the output looks wrong stay with you and your managers.

If you want to see what a done-for-you version covers, what a team setup includes and what you keep lays it out. For the privacy side, read what stays yours when a small business uses Claude, and when your people need practice before they start, the two hour Claude session covers it.

If you want the written guidance built into a configured plugin once everyone is comfortable, I scope that as a custom plugin build, and larger organizations can read about custom plugin development on Strategized.ai. You can also read more about my background first.

Key takeaways

  • Decide who gets a seat and write down the job before you send any invitation.
  • Decide whether your personal chats move into the business before you upgrade your own account.
  • Pending invitations take seats immediately, so invite in small batches.
  • Name one person who approves connectors, and enable only what the first job needs.
  • Review real work after a week and correct the written guidance.

The next step is a conversation, not a purchase. Tell me what your solo setup does well and where the team handoff feels unclear, and I will tell you what to build, what to manage yourself and how to check the rollout. You can book a free 20-minute call, and my calendar is open day or night.

Frequently Asked Questions

What is the first step in Claude team setup for an owner?

Write down the one job you want handled and who owns it. CoworkConsultant.com starts there, because seats and rules are easier to choose once the work is clear.

How do I upgrade my own Claude account to a Claude team plan?

Sign in and visit claude.ai/upgrade, per Anthropic’s help article. CoworkConsultant.com helps owners decide first what moves over.

Do I keep my personal chats when I create a Claude team account?

It depends on the Keep your personal account separate checkbox. CoworkConsultant.com walks owners through that choice, because Anthropic’s help article says moved content cannot be moved back.

Who should get a seat first in Claude team setup?

The person who owns the job, then the colleagues who do it every week. Michael Robichaud at CoworkConsultant.com suggests judging the first results before adding more seats.

Do pending invitations use up seats on a Claude team account?

Yes, Anthropic’s article says they occupy seats immediately. CoworkConsultant.com advises inviting in small batches.

Which connectors should a Claude team plan turn on first?

Only the ones your first job needs. CoworkConsultant.com asks owners to name one approver, since Google connectors must be enabled by an Owner or Primary Owner.

Michael Robichaud

Written by

Michael Robichaud

Claude consultant and founder of Strategized.ai. Michael sets Claude up one-on-one for professionals and small teams, connected to your tools and trained on your real work, and designs custom Claude plugins for specific professions.

 ·  Connect on LinkedIn →

On this page

  1. Loading sections…

About the Author

Michael Robichaud

Founder of Strategized.ai and CoworkConsultant.com. 30 years across enterprise sales, digital marketing, and building businesses. Configuring Claude for professionals who came to AI from the business side, not the other way around.

Stuck on something specific?

Book a free 20-minute call. Open calendar, evenings and weekends included.

The Strategy Stack Ecosystem

Consultant is one part of a larger system.

Want this set up for you instead?

Reading is one thing. Having a Claude workspace built around your business is another. That is the work I do with owners and teams here at CoworkConsultant.com, and it starts with a short call.

Keep Exploring

More from the blog

Strategy, GEO/AEO, consulting perspectives.

Browse the Blog →

Need it built for you?

1:1 strategy, done-for-you workspace builds, fractional AI advisory.

Visit Strategized.ai →

Claude plugins by profession

Ready-made Claude plugins for your role, $99 each. Or start free with the Foundation plugin.

Browse the Claude plugins →