Claude (Anthropic) User Management Guide

• Model type: role-based
• Description: Claude for Work uses a flat three-tier role model: Owner, Admin, and Member. Permissions are fixed per role; there are no custom roles or granular permission toggles available in the UI as of early 2025.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse - role assignment controls access to admin settings and billing only. No per-Project or per-feature permission scoping is available for individual members.

1. Sign in to claude.ai as Owner or Admin.
2. Navigate to Settings → Members (Team plan) or the Enterprise admin console.
3. Click 'Invite members'.
4. Enter the invitee's email address (one or multiple, comma-separated).
5. Select role: Member or Admin.
6. Click 'Send invites'. Each invitee receives an email with an acceptance link.
7. Seat is counted and billed once the invitation is accepted.

Required fields: Email address of invitee, Role selection (Member or Admin)

Watch out for:

• Invitations expire; if the recipient does not accept within the expiry window, the admin must resend.
• On Team plan, minimum 5 seats must be purchased; adding a user below that floor is not possible.
• On Enterprise, users provisioned via SCIM bypass the email invitation flow entirely - they are activated on first SSO login.
• There is no bulk CSV import available on the Team plan UI; bulk provisioning requires Enterprise + SCIM.

• Can delete users: No
• Delete/deactivate behavior: Anthropic does not expose a 'delete member' action in the admin UI. Admins can remove (deactivate) a member, which revokes workspace access immediately. The user's Anthropic account itself is not deleted. On Enterprise with SCIM, deprovisioning in the IdP triggers automatic access revocation via SCIM DELETE; the account record is retained.

1. Sign in to claude.ai as Owner or Admin.
2. Navigate to Settings → Members.
3. Locate the member to remove.
4. Click the '…' (more options) menu next to their name.
5. Select 'Remove from team'.
6. Confirm the action. Access is revoked immediately.
7. (Enterprise with SCIM) Alternatively, deprovision the user in Okta/Entra/Google Workspace; SCIM propagates the removal automatically.

Watch out for:

• Removing a user does not delete their conversation history; data retention follows Anthropic's data retention policy.
• On Enterprise, if SCIM is active, removing a user only in the Claude admin UI (without deprovisioning in the IdP) may result in the user being re-provisioned on next IdP sync.
• The Owner role cannot be removed by Admins; only the Owner can transfer or relinquish ownership via Anthropic support.
• There is no 'suspend' or 'deactivate without removing' state - removal is binary.

• Where to check usage: claude.ai → Settings → Billing (Owner only) shows current seat count and next billing date. Enterprise customers may have a dedicated account dashboard or receive usage reports from their Anthropic account team.
• How to identify unused seats: No built-in 'last active' or login-date column is exposed in the Team plan member list as of early 2025. Enterprise customers with audit logs enabled can query login events to identify inactive users. Admins should cross-reference the member list against IdP last-sign-in data when SCIM is active.
• Billing notes: Team plan seats are added incrementally and billed at the per-seat rate; removing a member mid-cycle does not generate a prorated credit on monthly billing (verify with Anthropic support for annual billing). Enterprise contracts set a minimum seat floor; unused seats within the contracted count are still billed.

On the Team plan, every provisioning and deprovisioning action is manual. Admins invite users one at a time (or comma-separated batches) via Settings → Members, and each invitee must accept an email link before the seat is active. There is no bulk CSV import on Team.

Removals are equally manual: locate the member, open the options menu, select 'Remove from team,' and confirm. Removal is binary - there is no suspend or deactivate-without-removing state. Without audit logs or a 'last active' column in the Team plan UI, identifying unused seats requires cross-referencing the member list against IdP sign-in data externally.

Ownership transfers are not self-serve and require contacting Anthropic support, adding friction to any org restructure or offboarding of a workspace Owner.

Recurring friction reported by Team plan admins centers on the SCIM gap: SSO is available, but without directory sync, every new hire and departure is a manual ticket. At scale, this creates meaningful operational drag.

Enterprise users flag Azure AD (Entra ID) SCIM sync delays of up to 40 minutes, which can leave access windows open longer than security policy allows during offboarding.

The absence of granular permission controls - no way to restrict specific features or Projects to subsets of members - is a consistent complaint across both tiers.

Common complaints:

• Team plan includes SSO but lacks SCIM provisioning, requiring manual member management at scale.
• Enterprise pricing is not publicly listed; prospective buyers must contact sales, and reported minimums (~$50K/year, 70+ seats) exclude smaller organizations.
• No 'last active' or usage analytics visible in the Team plan admin UI, making it difficult to identify unused seats.
• Ownership transfer requires contacting Anthropic support rather than being self-serve.
• Azure AD (Entra ID) SCIM sync delays of up to 40 minutes reported by Enterprise users.
• No granular permission controls - admins cannot restrict specific features or Projects to subsets of members.
• Invitation expiry behavior is not clearly communicated; expired invites require manual resend with no automated reminder.
• Removing a user in the Claude admin console without also deprovisioning in the IdP can result in re-provisioning on next SCIM sync.

Choose the Team plan if your organization is under the Enterprise seat minimum and can absorb manual provisioning overhead. SSO is included, which covers authentication; the gap is lifecycle automation.

Upgrade to Enterprise if you need SCIM-driven provisioning, audit logs for compliance, or the 500K context window for long-document workflows. Validate SCIM sync latency with your IdP before relying on it for time-sensitive offboarding - reported delays on Entra ID are a known issue.

If your IdP is not Okta, Microsoft Entra ID, or Google Workspace, confirm SCIM compatibility with Anthropic before committing, as only those three are officially listed.

Bottom line

Claude for Work is a capable AI workspace with a clean SSO story on Team and a full SCIM 2.0 implementation on Enterprise - but the gap between those two tiers is significant for IT teams.

Every app that depends on automated lifecycle management hits a wall on Team, and Enterprise's reported contract minimums mean smaller organizations may not qualify.

The flat role model and absent usage analytics add operational overhead that admins should factor into their evaluation alongside the AI capability itself.