Admin Reference Guide
Claude Admin Guide: Settings, Seats, and Team Management
Everything the person holding the keys needs to know, without the jargon.
If you have just been handed admin access to a Claude team or enterprise workspace, this page covers the controls that matter most. You will find a clear map of the settings console, how to add and remove members, what connectors and integrations you can govern, and the privacy limits that apply to admin visibility.
A Claude workspace admin can invite and remove members, assign roles, adjust workspace-level settings, and control which integrations or connectors are available to the team. Admins cannot read individual users' conversation history. The settings console is the central place for seat management, usage controls, and organization-wide defaults. Billing is handled separately and may require an owner or billing role depending on your plan.
Core Admin Controls
What You Can Manage from the Admin Console
The settings panel groups controls into a few key areas. Here is what each one covers.
Member Management
Invite members by email, assign roles such as member or admin, and remove access when someone leaves. Seat counts update as you add or remove people.
Workspace Settings
Set organization-wide defaults including the workspace name, default language, and whether members can create their own Projects or connect personal integrations.
Connectors and Integrations
Control which external tools, such as web search or file connectors, are available to your team. You can enable or disable these at the workspace level without touching individual accounts.
Roles and Permissions
Roles determine what each person can do inside the workspace. Admins can modify settings and manage members; standard members use Claude within the limits you set.
Billing and Plan
Depending on your plan, billing access may sit with an owner or a dedicated billing role. Admins typically can view seat counts and usage summaries but may not have full payment access.
Privacy and Visibility Limits
Admins can see aggregate usage data and which features are active, but conversation content stays private to each user. You cannot read chat transcripts.
Seat Management
Adding, Removing, and Reassigning Seats
To add a new team member, go to the Members section of the admin console and enter their email address. They will receive an invitation and gain access once they accept. You can assign their role at the time of invitation or change it afterward.
Removing a member revokes their access immediately. The seat becomes available for reassignment without requiring a separate cancellation step. If your plan has a fixed seat cap, you will see a warning when you approach the limit.
Some plans allow you to assign different permission levels, such as distinguishing between full admins and read-only or restricted members. Check your plan details, because the available roles vary by tier.
Integrations and Connectors
Governing What Your Team Can Connect
Workspace-Level Toggles
You can switch connectors on or off for the entire workspace. A connector disabled at the admin level is unavailable to all members, regardless of their individual settings.
Web Search Control
Web browsing or search capabilities can be enabled or restricted from the admin panel. This is useful for organizations with data-handling policies around external sources.
Third-Party App Access
If your plan supports OAuth-connected apps or API integrations, you manage which apps are permitted through the integrations section of the console.
Usage Summaries
Admins can view aggregate usage metrics such as message volume and active users. These summaries help with capacity planning but do not expose conversation content.
What Admins Cannot Do
Privacy Limits You Should Know
The most common admin misconception is that workspace access includes conversation visibility. It does not. Claude's design keeps conversation content private to the individual user. You will not find a panel that lets you read your team's chats, and there is no export tool for conversation history at the admin level.
Usage data you can see is aggregated and anonymized. You might see that the workspace sent a certain volume of messages in a given period, but you cannot attribute those messages to specific users or read their content. This applies to Projects as well: an admin who is not a member of a Project cannot view that Project's contents.
If your organization needs conversation logging or audit trails for compliance reasons, that capability sits at the API level, not the consumer product admin console. Teams with those requirements typically use the Claude API with their own logging layer rather than the standard team plan.
Learn to Get More From Claude as a Team
Knowing where the settings live is a start. Getting your team to use Claude effectively takes a different kind of skill. The Claude Academy curriculum is hands-on from the first lesson, built for people who learn by doing rather than reading documentation.
Frequently Asked Questions
Can a Claude admin read employees' chat history?
No. Conversation content is private to each user. Admins have access to workspace settings, member lists, and aggregate usage summaries, but cannot view individual chat transcripts. This holds true for conversations in personal Projects as well.
How do I add a new member to a Claude team workspace?
Go to the Members section of the admin console, enter the person's email address, choose their role, and send the invitation. They will receive an email and gain workspace access once they accept. The seat count updates automatically.
What is the difference between an admin and a member role in Claude?
Admins can access the settings console, manage members, change workspace defaults, and control integrations. Members use Claude within the parameters the admin has set. Some plans have additional roles, such as owner or billing-only access, for finer permission control.
Can I restrict what integrations my team uses?
Yes. Connectors such as web search and third-party app integrations can be toggled on or off at the workspace level from the admin console. A connector you disable is unavailable to all members, regardless of their individual preferences.
How do I remove someone from a Claude workspace?
Find the person in the Members list inside the admin console and select the option to remove them. Their access is revoked immediately. The seat becomes available for reassignment, and their account data stays private to them.
What usage data can admins see?
Admins can typically view aggregate metrics such as total message volume, number of active users, and which features the workspace is using. The data is rolled up at the workspace level. You cannot see per-user breakdowns or conversation content.
Can admins control whether members use Claude for personal projects?
Workspace settings can restrict certain features or integrations at the org level. Whether members can create personal Projects or connect individual accounts depends on the settings your plan exposes and what you choose to enable or disable in the console.
Who handles billing if I am an admin but not the account owner?
Billing access depends on how roles are configured on your plan. On many plans, full billing control sits with the account owner or a dedicated billing role. Admins may be able to view seat counts and usage but not update payment details. Check your plan's role documentation for the exact split.
Ready to Level Up Your Team's Claude Skills?
The best admin is the one whose team actually knows how to use the tool.