Team & Enterprise Admin Basics

9 examples to get you started with Team & Enterprise Admin - 6 basic and 3 intermediate.

Prerequisites

• A Team or Enterprise Claude plan. Free and Pro accounts do not expose multi-seat workspace management.
• Access to the email address that will become the workspace's first admin.
• If you plan to use SSO, have your identity provider admin contact ready before you reach the intermediate examples below.

Basic Examples

1. Creating Your First Workspace

The first thing any new admin does is create the workspace that will hold the whole team.

1. Sign in to the Claude Console.
2. Select "Create Workspace."
3. Name the workspace (usually the company or department name).
4. Confirm the plan tier (Team or Enterprise).
5. The creator is automatically assigned the admin role.

• The person who creates the workspace becomes its first admin automatically.
• A workspace name should be recognizable to everyone who will see it in billing and invite emails.
• You can create additional workspaces later for other departments if you want separate billing and access boundaries.

Related: How the Claude Console Organizes Workspaces, Seats, and Roles - the mental model behind what you just created.

2. Understanding Your Role After Signup

Right after creating a workspace, it helps to confirm what your admin role actually lets you do.

1. Console > Workspace Settings > Members.
2. Find your own name in the member list.
3. Confirm your role shows as "Admin."

• Admin is the role with the widest permissions: inviting members, changing settings, and managing billing access.
• Roles are scoped per workspace, so being an admin here says nothing about any other workspace you might join later.
• If your role ever shows as "Member" unexpectedly, someone else changed it, and you should check with another admin.

3. Inviting Your First Team Member

Once the workspace exists, the next step is bringing in the rest of the team.

1. Console > Workspace Settings > Members > Invite.
2. Enter the teammate's email address.
3. Choose their role: Admin, Member, or Billing.
4. Send the invite.

• Each invite consumes one seat once the person accepts, so seat count and invite count are directly linked.
• Choosing the right role at invite time avoids a follow-up settings change later.
• Invited members typically get an email with a link to accept and set up their own sign-in.

Related: Steps to Provision New Seats in the Claude Console - the full checklist for inviting and assigning seats.

4. Reading the Seats and Billing Summary

Every workspace has a summary screen showing how many seats are in use and what they cost.

1. Console > Workspace Settings > Billing.
2. Review "Seats used" vs. "Seats available."
3. Review the current plan tier and renewal date.

• Seats used counts every accepted invite, including admins, members, and billing-only roles.
• This screen is the fastest way to tell if you need to buy more seats before inviting additional people.
• Billing-role members can view this screen without needing full admin rights.

5. Locating the Admin Settings Panel

Admin settings are where workspace-wide configuration lives, separate from any individual member's account.

1. Console > Workspace Settings.
2. Review the tabs: Members, Billing, Security, and (Enterprise only) SSO/SCIM.

• Workspace Settings is only visible to admins; members see a reduced menu.
• The Security tab is where SSO gets configured on plans that support it.
• Settings here apply to the whole workspace, not to a single person's account.

6. Checking Your Plan Tier and Seat Count

Before inviting a large batch of people, confirm what your current plan actually allows.

1. Console > Workspace Settings > Billing > Plan Details.
2. Note the plan tier (Team or Enterprise).
3. Note the maximum or current seat count.

• Team and Enterprise plans differ in the admin and governance features available, not just price.
• Enterprise unlocks SSO, SCIM, and programmatic analytics access that Team does not include.
• Knowing your tier up front avoids inviting people into features your plan does not support.

Related: Understanding Claude's Plan Tiers: Free, Pro, Team, and Enterprise - a full comparison of what each tier includes.

Intermediate Examples

7. Assigning a Billing-Only Role

Some workspaces want finance staff to see invoices without giving them admin control over people.

1. Console > Workspace Settings > Members > Invite (or Edit for an existing member).
2. Set role to "Billing."
3. Confirm the person can see Billing but not Members or Security tabs.

• Billing role is deliberately narrower than admin, so finance staff cannot accidentally change who has access.
• This separation is useful in companies where IT and finance are different teams with different responsibilities.
• A person can be upgraded from Billing to Admin later if their responsibilities expand.

Related: How Roles and Permissions Control Workspace Access - a deeper look at what each role can and cannot do.

8. Preparing for SSO Before You Need It

Enterprise admins planning to onboard a large team benefit from setting up SSO before mass-inviting people.

1. Console > Workspace Settings > Security > SSO.
2. Confirm the workspace is on an Enterprise plan.
3. Gather identity provider details from IT before configuring the connection.
4. Decide whether SCIM auto-provisioning will accompany SSO.

• SSO lets employees sign in with their existing company credentials instead of a separate Claude password.
• Pairing SSO with SCIM means seats can be created and removed automatically as the company directory changes.
• This step is worth doing early, since retrofitting SSO onto a workspace with many manually invited members takes more cleanup.

Related: How SSO and SCIM Provisioning Work Together - the full explanation of how these two systems interact.

9. Auditing Who Has Admin Access

Periodically reviewing who holds the admin role keeps a workspace from accumulating unnecessary risk.

1. Console > Workspace Settings > Members.
2. Filter or sort by role to list every Admin.
3. Confirm each admin still needs that level of access.
4. Downgrade or remove anyone who no longer does.

• Admin access should track actual responsibility, not just seniority or tenure.
• A smaller admin list is easier to reason about and reduces the blast radius of a compromised account.
• This review pairs well with a recurring calendar reminder rather than being a one-time task.

Related: Team & Enterprise Admin Best Practices - broader guidance on provisioning, roles, and billing hygiene.

Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.