# Claude Team Roles: Owner vs Admin vs User

Claude Team owner vs admin: an Admin manages who's in, an Owner runs every setting. The roles, which job needs which, and who should hold each.

By Gabe Pérez. Published 2026-11-12.
Original: https://gabezen.com/blog/claude-team-owner-vs-admin/

Claude Team has four roles, and the product describes three of them in one line each. A **User** "Can create chats." An **Admin** "Can manage user membership," which means inviting and removing people. An **Owner** "Can manage user roles and organization settings," which is every switch that matters: connectors, capabilities, enterprise search, usage credits, billing. The **Primary owner** is an Owner with two extra powers, exporting the organization's data and handing the role on, and there's only one. When Claude or a course tells your staff to "ask your admin," the person they need is almost always an Owner.

Those three descriptions are from the Add member dialog in my company's own Team org. On November 12, 2026, I had Claude go through the settings pages of that org in Chrome, signed in as me, the Primary owner. It opened the Add member dialog, closed it without adding anyone, and changed no settings. The rest comes from Anthropic's help center and the Claude 101 course, read the same week.

## What are the roles in a Claude Team plan?

Four. The Members page labels them "Primary owner," "Owner," "Admin" and "User," and the Add member dialog offers the last three, with User as the default. You can't pick Primary owner there; it's moved from one person to another, never added.

Anthropic's [roles and permissions article](https://support.claude.com/en/articles/9267276-roles-and-permissions) has the full table:

| What the role can do | User | Admin | Owner | Primary owner |
|---|---|---|---|---|
| Create and modify chats, use projects | Yes | Yes | Yes | Yes |
| Invite new members, remove members, cancel invitations | | Yes | Yes | Yes |
| Enable native and custom integrations, capabilities, public projects, project sharing | | | Yes | Yes |
| View and pay invoices, add billing methods, provision new seats | | | Yes | Yes |
| Invite or remove Admins and Owners, modify roles | | | Yes | Yes |
| View usage analytics | | | Yes | Yes |
| Request data exports, request a Primary Ownership transfer | | | | Yes |

Two lines from the same page: "Team and Enterprise organizations can only have one Primary Owner," and "The Primary Owner seat uses one of your plan's licenses." Custom roles, where you build your own mix, are Enterprise only.

The table still says "integrations," while every newer page says "connectors." Same thing.

## Owner vs Admin: what can an Admin actually do?

Manage who's in the organization, and little else. An Admin can invite people, remove them and cancel invitations. Per Anthropic's [seats article](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans), an Admin can also "reassign seat types for members in Organization settings > Members." An Admin can't add a connector, flip a capability, finish enterprise search, turn on usage credits, buy seats or change anyone's role.

That's a narrow job for a 10-person firm, and it's the role people pick by mistake. The connectors article spells it out for one setting: "Only Owners and Primary Owners can change this setting. Other admins can see it but can't change it."

## Why does Claude 101 say "admin" when it means Owner?

Because the course uses "admin" loosely, and on Team the word is also the name of a weaker role. A few examples from [Claude 101](https://academy.claude.com/courses/claude-101):

- The [enterprise search lesson](https://academy.claude.com/courses/claude-101/enterprise-search) says it "must be enabled by a workspace admin," then later "For admins (Owners)." The help center says "Owners will need to complete this initial setup."
- The course page says "On Team and Enterprise, your admin controls whether designs, decks, and documents are available." Anthropic's artifacts guide is written for "Owners and Primary Owners."
- The artifacts lesson says "On Team an admin can turn them off," and the Chrome lesson says admins can turn it on or off. Both are Owner settings in the help center.

The product does it as well. Our enterprise search project reads "Created by your admin." Some help articles call the basic role a member ("the default member role"), though the roles table, the Members page and the Add member dialog all say "User." There's no "workspace admin" role in Claude Team. Read "admin" as "whoever holds Owner" and you'll be right nearly every time.

This mismatch runs through the whole course, so [the owner's side of Claude 101](https://gabezen.com/claude-101-owners-side/) goes lesson by lesson through what the Owner switches on first.

## Which role does each job need?

| Job | Who can do it | Source |
|---|---|---|
| Chat and projects | Everyone | [Roles](https://support.claude.com/en/articles/9267276-roles-and-permissions) |
| Invite or remove members | Admin, Owner, Primary owner | [Roles](https://support.claude.com/en/articles/9267276-roles-and-permissions) |
| Change someone's seat Tier (Standard or Premium) | Admin, Owner, Primary owner | [Seats](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans) |
| Buy seats, open Billing | Owner, Primary owner | [Seats](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans) |
| Make someone an Admin or Owner | Owner, Primary owner | [Roles](https://support.claude.com/en/articles/9267276-roles-and-permissions) |
| Add a connector for the organization, answer requests | Owner, Primary owner | [Connectors](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities) |
| Capabilities: web search, memory, code execution, enterprise search | Owner, Primary owner | [Roles](https://support.claude.com/en/articles/9267276-roles-and-permissions) |
| Finish enterprise search setup | Owner, Primary owner | [Enterprise search](https://support.claude.com/en/articles/12489464-use-enterprise-search) |
| Usage credits and spend limits | Owner, Primary owner | [Usage credits](https://support.claude.com/en/articles/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans) |
| Organization instructions (house rules in every chat) | Owner, Primary owner | [Organization instructions](https://support.claude.com/en/articles/14546867-set-organization-instructions) |
| Export all the organization's data, hand on Primary owner | Primary owner only | [Roles](https://support.claude.com/en/articles/9267276-roles-and-permissions) |

A few of these have a step outside Claude, too. Google may need your Workspace admin to trust Claude, Microsoft 365 needs a one-time consent from an Entra Global Administrator, and Slack needs a Slack admin to approve the app. Those are roles in other companies' products, and at a small firm they're often the same person as the Claude Owner. [Setting up enterprise search](https://gabezen.com/blog/claude-enterprise-search-setup/) walks through all three.

Seats have a wrinkle. The dialog's Tier options are "Standard seat" ("Basic usage") and "Premium seat" ("More usage than standard"). Admins can move people between them. The seats article says a Standard to Premium upgrade is charged "the price difference immediately," yet the roles table gives Admins no billing rights. I didn't test whether an Admin's upgrade goes through and charges you.

## Who do staff see when they're told to ask an admin?

The Primary owner, unless you change it. In Organization settings > Organization and access there's an "Internal help contact," and it says "By default, they see the primary owner in their account settings." So every "ask your admin" in your org leads to one person's desk. If that's you and you'd rather it were your operations manager, that's the setting. I didn't change ours.

Claude Academy sends people to an admin too. Its help page tells a learner who isn't linked to the company yet to "Ask your organization's Claude admin to add you." An Admin can add the person to the organization; whether Academy needs anything more, its help page doesn't say.

## What's the difference between Primary owner and Owner?

Two powers: exporting all the organization's data, and handing the Primary owner role to someone else. Otherwise they're the same. If you're unsure who it is, Anthropic says to look in Settings > Account.

Pick the person your team would trust with a copy of everything, since the export includes everyone's chats. Who that should be, and what the export shows, is in [the employer post](https://gabezen.com/blog/can-my-employer-see-my-claude-chats/#who-should-be-the-primary-owner-of-a-claude-team). How to hand the role on is in [Claude Team plan setup](https://gabezen.com/blog/claude-team-plan-setup/#who-should-be-the-primary-owner-and-how-do-i-change-it). Do it before anyone's last day.

## Can a Claude Team have more than one Owner?

Yes. Only Primary owner is limited to one, and Anthropic now nudges you to add a second Owner. Organization and access in our org opens with a checklist called "Get your team on Claude": "Set up SSO," "Add another Owner," "Invite your members," "Verify your domain."

## Who should hold which role in a 10-person firm?

Here's how I'd split it.

- **Primary owner:** the founder or managing partner, the person the team would trust with an export of everything.
- **A second Owner:** whoever will run Claude day to day, often the operations manager or the partner who uses it most. Then a holiday, a sick week or a resignation doesn't stop anyone from adding a connector. In our org I'm the Primary owner and my cofounder is an Owner, for exactly that reason.
- **Admin:** usually nobody. At ten people, inviting and removing someone takes an Owner a minute. Give Admin only to someone who handles joiners and leavers and shouldn't touch settings, like an office manager at a firm whose partners want the settings to themselves.
- **Everyone else:** User.

Don't hand out Owner to make a problem go away. An Owner can change what every connector may do, who sees shared chats and what the bill can grow to. Two or three is plenty.

If you bring someone in to set Claude up, they'll need Owner while they do it, because nearly every setup step is an organization setting. Take it back when they're finished.

## What I couldn't confirm

- **What an Admin sees.** I tested as the Primary owner, not as an Admin, so I can't say which settings pages an Admin can open read-only.
- **Usage analytics.** The roles table gives them to Owners and the Primary owner only. I couldn't check what an Admin sees. Claude Academy's org reports, a different page about who finished which course, are open to "Primary owner, Owners, and Admins."
- **Admins and Premium seats.** Whether an Admin's Standard to Premium upgrade charges you, as the seats article suggests.
- **Role-based permissioning.** Anthropic's Team plan page lists it as a feature, while the roles article says custom roles are Enterprise only. Our Add member dialog offered only User, Admin and Owner.

## What should I do next?

Open Organization settings > Members and look at the Role column. If you're the only Owner, add a second one today. If someone is an Admin because a lesson said "admin," make them an Owner or a User. Then score the rest of your org with [the ten-question team check](https://gabezen.com/check/), no email needed.

If you'd rather have it done, [my setup](https://gabezen.com/pricing/#build) starts at $3,997 for one team of up to 25, and you pay for your own seats. One job live on your real work by day 14, or all your money back. It has you add me to your Claude Team, so ask which role I'd hold.

---

More posts: https://gabezen.com/blog/
The whole site in one file: https://gabezen.com/llms.txt