THE FUTURE MARKETACADEMY
Your classroomRoom 01 · AI Lab
School of AI

Claude for Teams: shared Projects, workflows and standards

Step 6 of 7 in AI Lab

Next in your path: 1.10.3 AI Study Systems: long-term learning projects

What you'll be able to do
  • Explain how a Team plan is organised: owners, admins, members and seats.
  • Add and remove members safely and know what single sign-on (SSO) changes.
  • Share a Project with the right permission and write project instructions that act as a team standard.
  • Provision and share skills so everyone gets the same recipe for the same job.
  • Add connectors for the organization, limit their tools and understand how each person signs in.
  • Review privacy, memory and data settings, and write a one-page team rollout plan.

Before this course: Claude Power Tools: Skills, Connectors (MCP), Claude Code and agents (course 1.12), and Claude Step by Step (course 1.11). You should already know Projects, skills and connectors for one person. Here we use them for a group. The Future Market Academy is not affiliated with Anthropic. Menu names come from Anthropic's Help Center as of 2026-11-12 and some screens are being renamed (for example "Customize" is becoming "Plugins"), so look for the closest name. Plans, limits and prices change: check Anthropic's pricing page before you buy.

Words in this course 43Open the Vocabulary Hall
01

From one person to a team: plans and roles

In simple words

When you use Claude alone, it is like cooking at home. A team is like a restaurant kitchen: everyone needs a role, a clear recipe and rules about who holds the keys. First we learn who does what.

Key facts
  • Before this course: Claude Power Tools (course 1.12). You already know skills, connectors and Projects for one person.
  • A Team plan needs at least two members and is not meant for individual use. The Team plan supports up to 150 seats; larger organizations are pointed to the Enterprise plan (Help Center).
  • Team plan members get access to the models, Claude Code, Cowork and Projects, plus connectors such as Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack (Help Center, What is the Team plan?).
  • The person who creates a Team needs a business email address. Every invited member needs an email on one of the organization's allowed domains.
  • If you already have a personal account on that email, the new Team is separate and your old chats and projects stay in the personal account. When you upgrade a personal account, content moved into an organization can't be moved back, and public projects become private.
  • Roles on Team and Enterprise (Help Center, Roles and permissions):
RoleWhat it is for
Member (called User in some Enterprise articles)Create chats and use Projects
AdminEverything a member does, plus inviting and removing members
OwnerAdmin powers, plus managing Admins and Owners and roles
Primary OwnerOwner powers, plus data exports and ownership transfers. Only one per organization
Custom (Enterprise only)No default permissions; access comes from custom roles
  • Only Owners and Primary Owners can open Organization settings > Billing and purchase seats. Owners and Primary Owners cannot remove themselves from the team; another Owner must do it.
  • Team plans have spend controls and centralized access and billing management.
Step by step
  1. Write down your team: names, jobs, and what each person uses Claude for.
  2. Decide who will be the Primary Owner (one person) and who will be Owners and Admins. Keep the number of Owners small.
  3. Check that everyone has an email on your organization's allowed domain.
  4. If you are on a Team plan, open claude.ai, then Organization settings and look at Members, Billing and Capabilities.
  5. Fill a table: Person, Role, Why they need it.
  6. Check: every role in your table has a reason, and nobody has more power than their job needs.
LESSON 01From one person to a team: plans and roles
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
Read the video script
[Host] "Claude for one person is simple. Claude for a team needs roles and rules."
[Text on screen: Team plan: 2 members minimum] "A Team plan needs at least two members."
[Text on screen: Primary Owner, Owner, Admin, Member] "Roles go from Member up to Primary Owner. There is only one Primary Owner."
[Text on screen: Billing: Owners only] "Only Owners and Primary Owners can open billing and buy seats."
[Host] "Give each person the smallest role that does the job."
Try it now

Draw your team's role table. For each person write the role and one sentence on why. Ask a colleague to challenge any Owner or Admin on your list.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Claude for Teams: shared Projects, workflows and standards" on The Future Market. Lesson 1: "From one person to a team: plans and roles".

What the lesson teaches:
- Before this course: Claude Power Tools (course 1.12). You already know skills, connectors and Projects for one person.
- A Team plan needs at least two members and is not meant for individual use. The Team plan supports up to 150 seats; larger organizations are pointed to the Enterprise plan (Help Center).
- Team plan members get access to the models, Claude Code, Cowork and Projects, plus connectors such as Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack (Help Center, What is the Team plan?).
- The person who creates a Team needs a business email address. Every invited member needs an email on one of the organization's allowed domains.
- If you already have a personal account on that email, the new Team is separate and your old chats and projects stay in the personal account. When you upgrade a personal account, content moved into an organization can't be moved back, and public projects become private.
- Roles on Team and Enterprise (Help Center, Roles and permissions):
- Role - What it is for

The exercise I'm working on:
Draw your team's role table. For each person write the role and one sentence on why. Ask a colleague to challenge any Owner or Admin on your list.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "From one person to a team: plans and roles" from the course "Claude for Teams: shared Projects, workflows and standards".

Here's what the lesson says:
When you use Claude alone, it is like cooking at home. A team is like a restaurant kitchen: everyone needs a role, a clear recipe and rules about who holds the keys. First we learn who does what.

The activity:
Draw your team's role table. For each person write the role and one sentence on why. Ask a colleague to challenge any Owner or Admin on your list.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Open Claude
Sources
My notes
02

Add and remove people safely

This lesson is part of full access: every course and every level for one payment.

03

Shared Projects as team workspaces

This lesson is part of full access: every course and every level for one payment.

04

Team skills: one recipe for everyone

This lesson is part of full access: every course and every level for one payment.

05

Standard prompts and outputs

This lesson is part of full access: every course and every level for one payment.

06

Connectors for the whole team

This lesson is part of full access: every course and every level for one payment.

07

Privacy, memory and a rollout plan

This lesson is part of full access: every course and every level for one payment.

++

Final project

This lesson is part of full access: every course and every level for one payment.

??

Quiz

  1. How many members does a Team plan need at minimum?

  2. Which role is limited to one per organization?

  3. Who can open Organization settings > Billing and buy seats?

  4. How long do invitation emails last?

  5. What are the two project permission levels?

  6. Which project visibility keeps it to you and invited members?

  7. Are shared skills editable by the people you share them with?

  8. What can an owner do to add a connector for the team?

  9. Does adding a connector to the team give everyone access?

  10. What are the three org-wide tool permissions for a connector?

  11. Can owners read members' individual memories?

  12. What does Anthropic say about training on Team and Enterprise data by default?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.