Steps to Provision New Seats in the Claude Console
Provisioning a new seat means inviting a person into a workspace, giving them the right role, and confirming they can actually sign in and use Claude under the company's plan.
This checklist walks through that process end to end, from checking available seats to confirming the new person's first login.
How to Use This Checklist
- Walk the steps in order the first time you provision a seat, then use it as a quick reference afterward.
- Confirm each step before moving to the next; skipping the role assignment step is the most common cause of follow-up support requests.
- Keep a running note of who has which role so the periodic access review described in this section's best practices page is easy to do later.
- Revisit this checklist whenever your company's identity provider setup changes, since that can shift some of these steps to be automatic.
Provisioning Steps
- Confirm available seats. Check the workspace's billing summary to see how many seats are already in use against the plan's total, so you know whether inviting this person requires buying an additional seat.
- Confirm the plan tier supports the access you need. Team supports manual multi-seat invites; Enterprise additionally supports SSO and SCIM-based automation, which changes several of the steps below.
- Decide the person's role before inviting them. Choose admin, member, or billing based on what they actually need to do, not out of convenience.
- Open the workspace's Members screen. This is where invites are sent and existing seats are managed, under Workspace Settings in the Claude Console.
- Enter the invitee's work email address. Using their company email keeps the seat tied to an identity the company controls, which matters for offboarding later.
- Select the role for the invite. Assign admin, member, or billing at invite time so the person's access is correct from their very first login.
- Send the invite. The invitee receives an email with instructions to accept and complete their sign-in setup.
- Confirm the invite status. Check that the invite shows as "pending" immediately after sending, and follow up if it does not appear at all.
- Wait for acceptance, or follow up if it stalls. An invite that sits pending for more than a few days is worth a direct nudge, since email invites are sometimes missed or filtered.
- Verify the seat count updated. Once accepted, confirm the workspace's seats-used count increased by one, confirming the seat is now billed and active.
- Confirm the new member's role is correct. Re-check the Members screen after acceptance to make sure the role that was set at invite time actually took effect.
- For SSO/SCIM-enabled Enterprise workspaces, confirm the person appears via directory sync instead of a manual invite. In this setup, adding the person to the right group in the company's identity provider is usually what actually provisions the seat, and steps 4-9 may be handled automatically.
- Point the new member to a starting resource. A short note pointing them to the workspace's usage guidelines or an onboarding page saves early support questions.
- Log the provisioning for your own records. Even a simple note of who was invited, when, and with what role makes later access reviews far faster.
- Schedule a follow-up review. Add this new seat to whatever periodic access review cadence the workspace already uses, so its role and necessity gets reconsidered over time, not just set once and forgotten.
Applying the Checklist in Order
- Confirmation steps (1-3): come first because they're the cheapest to fix; catching a seat-count or role mistake before sending an invite avoids an awkward follow-up correction.
- Invite and acceptance steps (4-11): are the mechanical core of provisioning and differ little between Team and Enterprise, aside from Enterprise's optional SSO/SCIM shortcut in step 12.
- Follow-through steps (13-15): are easy to skip but are what keeps a growing workspace's access list accurate and auditable months later.
FAQs
Do I need to check available seats before every invite?
Yes, especially on plans with a fixed seat count. Sending an invite that exceeds the current seat allocation can trigger an unexpected billing change, so it's worth confirming first.
What role should most new hires get?
Member, in most cases. Admin should be reserved for the people actually responsible for running the workspace, and billing for finance staff who only need invoice visibility.
Can I change someone's role after they've already accepted an invite?
Yes. Roles can be changed at any time from the Members screen; the invite-time role is just the starting point, not a permanent assignment.
What happens if an invite sits pending for a long time?
It simply waits until accepted or revoked. It's worth following up directly if it sits unaccepted for more than a few days, since invite emails are sometimes missed.
Does provisioning work differently on Enterprise plans with SSO?
Yes. If SCIM provisioning is configured alongside SSO, adding someone to the right group in the company's identity provider can provision their seat automatically, skipping the manual invite steps.
Why does the checklist recommend logging each provisioning action?
A simple record of who was invited, when, and with what role makes later access reviews dramatically faster, especially once a workspace has dozens of seats.
What's the most commonly skipped step?
Confirming the role actually took effect after acceptance. Admins often assume the invite-time role stuck without double-checking, which occasionally surfaces as a support request later.
Should I use a personal or work email when inviting someone?
A work email, when available. Tying the seat to a company-controlled identity makes offboarding cleaner, since the seat's access is tied to an account the company can deactivate.
Is there a limit to how many people I can invite at once?
The practical limit is whatever seat count your plan allows; beyond that, you would need to increase your seat allocation before continuing to invite new people.
How does this checklist relate to offboarding?
It's the mirror image: provisioning adds a seat and role deliberately, and offboarding removes or downgrades it deliberately. Logging provisioning actions, as recommended in step 14, makes offboarding far easier to get right.
Do billing-role invites follow the same steps?
Yes, the process is identical; only the role selected in step 6 changes. A billing invite grants payment and cost visibility without the broader admin permissions.
Related
- How the Claude Console Organizes Workspaces, Seats, and Roles - the underlying model this checklist walks through in practice.
- How Roles and Permissions Control Workspace Access - detail on choosing the right role at step 3 and 6.
- How SSO and SCIM Provisioning Work Together - the automated alternative referenced in step 12.
- Workspace Setup Checklist for New Enterprise Admins - the broader checklist this seat-provisioning process fits inside.
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.