Admin Roles: Who Controls What in Your Team Workspace
Assigning the right roles from the start prevents billing confusion, unauthorized changes, and the chaos of everyone thinking someone else is handling admin. Five-minute read that saves headaches later.
The Three Roles
| Role | Can Do | Cannot Do |
|---|---|---|
| Primary Owner | Everything below, plus: own the billing account, set the plan, receive billing emails | Transfer Primary Ownership to anyone else |
| Owner | Invite and remove members, change member roles, edit workspace settings, manage shared Projects | Remove or change the Primary Owner |
| Member | Use Claude, create their own Projects and chats, use shared Projects if permitted | Access billing, invite members, change settings |
Primary Ownership cannot be transferred. Whoever clicks "Start your Team" is Primary Owner permanently. If that person leaves Empower, Anthropic support can assist, but it's a manual process. Choose carefully.
Who Should Be What
Primary Owner — one person, usually you
Pick someone who:
- Pays for or controls the budget
- Will remain with Empower long-term
- Doesn't need to delegate billing decisions
Do not hand this to an assistant or IT person unless they have permanent authority over budget. If your assistant sets it up and then leaves, recovery is a manual process.
Owners — 1 to 2 trusted admins
People who can add a new hire on day one, remove a departing employee immediately, and adjust workspace settings.
Good candidates at Empower: an operations lead, a trusted manager, or an office coordinator handling onboarding. One Owner is usually enough. Two is fine if they coordinate. Three-plus creates conflicting actions — someone adds seats while another removes them, and nobody owns the bill.
Don't make your whole leadership team Owners. It's tempting ("everyone can manage it"). In practice it means nobody does. Keep it tight.
Members — everyone else
Normal users. Chat, build Projects, use shared Projects, do their work. They can't touch billing or invite anyone.
The right role for:
- Account managers, operations staff, field team, admin
- Any outside advisor or consultant using the workspace temporarily
Common Setup Patterns
Small team (5–10)
- 1 Primary Owner (principal)
- 1 Owner (office manager or ops lead)
- Everyone else: Member
Mid-size (10–30)
- 1 Primary Owner
- 2 Owners (ops lead + one backup, so coverage exists when one is traveling)
- Everyone else: Member
With outside consultants — Members. Remove at engagement end; access stops immediately.
Changing a Role
- Settings → Members (or https://claude.ai/settings/members).
- Find the person.
- Click their current role, select the new one.
Takes effect immediately. No need to remove and re-invite.
Removing Someone Immediately
When someone leaves Empower, remove them that day — not next week.
- Settings → Members
- Click the person
- Remove from workspace
They lose access on confirm. Any Projects they created remain in the workspace — you don't lose their work.
Audit quarterly. Every three months, scan the member list. Remove anyone who left. Confirm the two people with Owner access are still the right two people. Check seat count vs. active users — you're paying per seat whether it's used or not.
Try This Now (3 min)
Open Settings → Members and write down:
- Who is Primary Owner?
- Who is/are Owners?
- Is there anyone listed who shouldn't be (left Empower, engagement ended)?
Fix any mismatch now.
What Comes Next
With roles set, the next topic is letting Claude handle longer tasks asynchronously — in the background while you do other work. Continue to Lesson 12.