Claude Administration
Claude admin console: what it controls and where to find it
A plain how-to for IT and operations leads on what Claude admins can manage, taken from Anthropic's own documentation as read on 5 November 2026. Settings change, so check the cited pages before you act.
The Claude admin console is where an organization's admins manage members and seats, spend and usage limits, and, for API organizations, workspaces. Anthropic does not use that exact phrase on its pages; it documents Organization settings in claude.ai for Enterprise plans, and the Claude Console (Claude Platform) at platform.claude.com for API organizations. Each fact below is cited to Anthropic with the date we read it, 5 November 2026.
plain answer
What the Claude admin console is
The Claude admin console is the admin area of an organization's Claude account. Anthropic documents it in two places, so it helps to know which one you have.
If your organization uses Claude through claude.ai on an Enterprise plan, admins work in Organization settings. If your organization uses the Claude API, admins work in the Claude Console (Claude Platform) at platform.claude.com, and Anthropic's Admin API page describes setting up your organization there to add members. That page describes the Admin API as a way to manage members, workspaces, invites and API keys programmatically, instead of by hand in the Claude Console.
Sources: Anthropic Admin API page (https://platform.claude.com/docs/en/manage-claude/admin-api) and Help Center article "What is the Enterprise plan?" (https://support.claude.com/en/articles/9797531-what-is-the-claude-team-plan), both read 5 November 2026.
how to
How do you manage members and seats?
Managing members and seats in the Claude admin console starts at Organization settings. Anthropic's Help Center says seat types appear under "Organization settings > Members" (read 5 November 2026).
Anthropic's user management page (read 5 November 2026) describes what an admin can do with members for Claude Enterprise: list them, change a role, remove them, and invite new ones. Removing a member returns the seat they occupied to the organization's pool. An invite stays pending until the person accepts it or it expires, and a pending invite can use a seat.
That page lists five Enterprise roles: user, managed, owner, membership admin and primary owner. It says the owner, membership admin and primary owner roles are assigned in claude.ai organization settings. Organizations whose identity provider creates users automatically cannot create invites through the API.
For API organizations, Anthropic's Admin API page describes setting up your organization in the Claude Console to add members (read 5 November 2026). We did not read an Anthropic page listing the Team plan's admin roles, so this page does not describe them.
how to
What spend and usage limits can admins set?
Spend limits are one of the things admins can set. Anthropic's Help Center says admins "can set spend limits at the organization and individual user levels to manage costs" and that seat-based plans also have per-seat usage limits (read 5 November 2026).
Anthropic's Spend Limits API page (read 5 November 2026) says admins of Claude Enterprise organizations can set a limit on each member, see where each member's limit is inherited from, and act on members' requests for a higher limit. It states the feature is for Claude Enterprise only and not available to Claude Console organizations.
For API organizations, Anthropic's Workspaces page (read 5 November 2026) says rate limits are set on the Rate limits page of the Claude Console and the monthly spend cap and alerts for an additional workspace are set from its Spend limits panel on the Workspaces page. The Default Workspace cannot have spend limits.
how to
How do workspaces work in the Claude Console?
Workspaces are the Claude Console's way to separate projects, environments or teams. Anthropic says workspaces keep "centralized billing and administration" while letting you assign members, service accounts, API keys and resource limits to each one (Workspaces page, read 5 November 2026).
The page's workspace roles include Workspace User (playground only), Workspace Developer (create and manage API keys, use the API), Workspace Admin (full control over workspace settings and members), Workspace Billing (view billing, inherited from the organization billing role) and Workspace Limited Developer. Organization admins automatically get Workspace Admin access to every workspace.
Anthropic's user management page (read 5 November 2026) lists workspaces as not available for Claude Enterprise (claude.ai) organizations, so this section applies to API organizations only.
security
What does Anthropic say about security and data settings?
Anthropic's Help Center article lists audit logs, SCIM provisioning, custom data retention controls and customer-managed encryption keys as Enterprise plan security features (read 5 November 2026). The article does not say whether admins configure each of them in Organization settings, so this page does not either.
For compliance, certification or data-handling questions, take them to Anthropic directly and read its current documentation. For questions about a connected system such as Salesforce, the vendor's own documentation is the source; our Claude and Salesforce guide lists what it says. Microsoft 365 add-ins such as Claude for Outlook have their own admin consent steps. Kriv does not give legal or compliance advice.
kriv role
Where Kriv helps
Kriv AI helps organizations plan a Claude rollout: who gets seats, how roles map to your teams, and who owns the admin settings after launch. Slack has its own admin setup, covered in our guide to Claude and Slack. Kriv AI has achieved the Select partner tier in the Claude Partner Network Services Track.
Kriv does not replace Anthropic's documentation, and the settings your plan includes are Anthropic's to confirm. Connector settings are a separate set of admin decisions; our Claude and Jira guide is one worked example.
limits
What this page could not confirm
Anthropic does not publish one page listing every admin console setting for every plan, and the pages we read did not describe menu layouts. We did not read Team-plan admin role definitions, single sign-on provider lists, audit-log scope or data retention options. For anything not cited above, open your own Organization settings or Claude Console and check Anthropic's current pages.
Sources
Cited sources
Related resources
Continue exploring
Straight answers
Frequently asked questions about Claude admin console: what it controls and where to find it
What is the Claude admin console?
It is the admin area of an organization's Claude account. Anthropic documents Organization settings in claude.ai for Enterprise plans and the Claude Console (Claude Platform) at platform.claude.com for API organizations (Anthropic Help Center and Admin API page, read 5 November 2026).
Who can access it?
Anthropic says administrative roles such as owner, membership admin and primary owner are assigned in claude.ai organization settings, and organization admins in the Claude Console get Workspace Admin access to all workspaces (read 5 November 2026).
Can admins set spend limits?
Yes. Anthropic says admins can set spend limits at the organization and individual user levels (Help Center, read 5 November 2026). Per-member limits via the API are Claude Enterprise only.
Can the admin console be automated?
Anthropic's Admin API lets you manage members, workspaces, invites and API keys programmatically instead of by hand in the Claude Console (read 5 November 2026). Which endpoints apply depends on your organization type.
Does Kriv run my admin console?
No. Your own admins hold the access. Kriv AI advises on roles, seats and rollout planning.
Talk to the team that would do the work
Bring your requirements to a working session with the person who'll actually deliver.
Book a Discovery Call