Claude for Government administrator guide changedgovernment/overview
Nearest release: v2.1.319, published 15 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 6 Nov 2026 16:05 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 6 Nov 2026 16:07 UTC.
Upstream edited
Recorded here
Lines+28added
Lines−101removed
From line
4
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
### Tenant ### Organizations ### Users ## Billing accounts ### A note on tenant administrators ## Where to go next
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55> **Who this guide is for:** Administrators who set up and manage Claude for Government for their agency.
66
7> **Find your section:**
7This guide covers the portals used to manage Claude for Government: how access, seats, and usage are organized, and who is responsible for each part. Members use Claude in the Claude apps, such as Claude Desktop, that your agency [makes available](https://claude.com/docs/government/config/settings.md#product-availability). Claude for Government isn't available in the Claude mobile apps.
8
9> [!NOTE]
810>
9> | If you are… | Start with |
10> | - | - |
11> | A tenant administrator | [Tenant administration](https://claude.com/docs/government/tenant-admin/overview.md) |
12> | An organization owner | [Organization administration](https://claude.com/docs/government/org-admin/overview.md) |
13> | Any user | [Your account](https://claude.com/docs/government/account/overview.md) |
14> | Anyone using Claude Desktop | [Use Claude Desktop](https://claude.com/docs/government/desktop/plugins.md) |
11> These cases are covered on other pages:
12>
13> * **Managing your whole tenant**: see [Tenant administration](https://claude.com/docs/government/tenant-admin/overview.md)
14> * **Managing one organization**: see [Organization administration](https://claude.com/docs/government/org-admin/overview.md)
15> * **Setting up a new tenant**: see [Tenant setup wizard](https://claude.com/docs/government/tenant-admin/setup-wizard.md)
16> * **Checking your own profile, usage, or sessions**: see [Your account](https://claude.com/docs/government/account/overview.md)
17> * **Using Claude Desktop**: see [Video walkthroughs for Claude Desktop](https://claude.com/docs/government/desktop/video-walkthroughs.md)
18> * **Installing Claude Desktop on agency devices**: see [Connect Claude Desktop to Claude for Government](https://claude.com/docs/government/deploy-desktop/configure.md)
19> * **Reviewing security and data handling**: see [Security and data handling](https://claude.com/docs/government/security/security-and-data-handling.md)
1520
16This guide covers the portals used to manage Claude for Government: how access, seats, and usage are organized, and who is responsible for each part.
17
18If you just want to use Claude for Government, you don't need this guide. You can simply sign in and start a conversation, and come back here when you need to manage other people's access or understand why something is configured the way it is.
19
2021## How your deployment is organized
2122
2223Claude for Government is organized as a three-level hierarchy:
2324
24**Tenant** → **Organizations** → **Users**
25* **Tenant**: The tenant is the top level, and it represents your agency's overall deployment. The tenant is managed by a short list of [tenant administrators](https://claude.com/docs/government/tenant-admin/admins.md).
26* **Organizations**: An organization is a group of users who share a pool of seats and a set of policies, with its own spend caps. Each organization has its own owners, its own members, its own seat assignments, and its own configuration. The organizations all share the tenant's single sign-on connection, so you configure identity once and every organization uses it.
27* **Users**: A user never belongs to more than one organization at a time. Each user has a [role](https://claude.com/docs/government/org-admin/users.md#understanding-roles), which decides what they can manage, and a [seat tier](https://claude.com/docs/government/org-admin/seat-tiers.md), which decides which models they can use and how much. A user with no seat tier can sign in and see their account, but they can't send messages to Claude.
2528
26### Tenant
29You might create one organization for each bureau, office, or program, or you might run the whole agency as a single organization. You would create more when you need any of the following:
2730
28The tenant is the top level, and it represents your agency's overall deployment. There is exactly one tenant per agency, and it holds the things that are shared across everyone: your connection to your identity provider for single sign-on, automatic user provisioning (where your directory system creates and updates accounts for you), the list of verified email domains, and the pool of credits and seats issued to you by Anthropic.
31* Separate billing accounts so one group's usage never draws down another group's balance
32* Separate usage reporting for each bureau or program
33* Different product settings, seat tiers, or access rules for different parts of your agency
2934
30The tenant is managed by a short list of **tenant administrators**. They create organizations, decide how seats are divided among them and what spend caps are set, and set policies that apply across the whole agency.
35A **billing account** is where your agency's credits and seats live. Anthropic sets up one or more billing accounts with your agency. Every organization is linked to exactly one billing account. Several organizations can share the same billing account, or each organization can have its own. Tenant administrators divide each billing account's [seat pool](https://claude.com/docs/government/tenant-admin/seats.md#how-seats-are-organized) among the organizations it funds, and can set per-organization [spend caps](https://claude.com/docs/government/tenant-admin/credits.md) to control how much any one organization draws from a shared balance.
3136
32### Organizations
33
34An organization is a group of users who share a pool of seats and a set of policies, with its own spend caps. You might create one organization for each bureau, office, or program, or you might run the whole agency as a single organization.
35
36Most agencies start with a single organization. You would create more when you need any of the following:
37
38* Separate billing accounts so one group's usage never draws down another group's balance.
39* Separate usage reporting for each bureau or program.
40* Different product settings, seat tiers, or access rules for different parts of your agency.
41
42Each organization has its own owners, its own members, its own seat assignments, and its own configuration. The organizations all share the tenant's single sign-on connection, so you configure identity once and every organization uses it.
43
44### Users
45
46A user is a single person. Every user belongs to exactly one organization, and two properties control what they can do:
47
48* A user's **role** determines what they can manage. Most people have the **User** role, which means they use Claude but don't administer anything. **Owners** and **Primary Owners** manage the organization: they manage members' roles and seats, and adjust organization-level settings.
49* A user's **seat tier** determines how much they can use Claude. A seat tier is a named bundle of usage limits (for example, how much Claude usage a person gets in a given period). A user with no seat assigned can sign in and see their account, but they can't send messages until an owner assigns them a seat.
50
51A user never belongs to more than one organization at a time. Moving a person between organizations keeps the same account; their role and seat assignment are managed separately in the new organization.
52
53## Billing accounts
54
55A **billing account** is where your agency's credits and seats live. Anthropic sets up one or more billing accounts with your agency, and each one holds a prepaid credit balance (a dollar amount that is drawn down as people use Claude) and a pool of seats (a fixed number of seats in each tier).
56
57Every organization is linked to exactly one billing account, and usage by that organization draws directly from the account's balance. Several organizations can share the same billing account, or each organization can have its own. Tenant administrators divide each billing account's seat pool among the organizations it funds, and can set per-organization spend caps to control how much any one organization draws from a shared balance.
58
5937## The three views
6038
6139<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-01-finding-your-way-around.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=e815e7d6b488de1c9629bfaa2f1354ab" aria-label="Video walkthrough: Finding your way around" />
from line 40
6240
6341Video: Finding your way around (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
6442
65> [accordion] Transcript
66>
67> Your tenant is your agency's deployment and holds its organizations. Each user belongs to one, run by Owners and Primary Owners. Tenant administrators manage the tenant.
68>
69> This video shows the web portal, which you open in a browser. Members use Claude in the Claude Desktop app, with Chat, Cowork, and Code.
70>
71> In a browser, open your agency's Claude for Government address and enter your work email.
72>
73> Select Continue, and your agency's usual sign-in page opens.
74>
75> After your agency's single sign-on, acknowledge the system-use notification.
76>
77> As an organization owner, Marcus lands on the admin view. With several organizations, tenant administrators pick one from the organization menu at the top of the page.
78>
79> Under People, Users lists each member's role and seat tier. Owners and Primary Owners manage these.
80>
81> Under Settings, Readiness lists anything blocking members from using Claude. Every step here is complete.
82>
83> The footer holds the view links. Select Switch to user view.
84>
85> The Account view shows your profile, usage, and sessions. Members who are not owners land here. Marcus is a Primary Owner and, separately, a tenant administrator.
86>
87> Switch to admin view takes you back.
88>
89> Tenant administrators also get Switch to tenant view.
90>
91> The tenant view covers every organization, with identity, seats, settings, and admins. Select an organization's name to open its admin view.
92>
93> Until setup is complete, Resume setup sits above the navigation.
94>
95> The dot on Settings flags Readiness. Its second card lists each organization, and Research Office still needs seats. Expand the row for its checklist, then follow Open to fix it.
96>
97> Admins, under Settings, lists the tenant administrators. Keep at least two.
98>
99> Switch to org view returns to the organization admin view.
43[Transcript](https://claude.com/docs/government/video-walkthroughs.md#finding-your-way-around)
10044
101The portal has three views. Which ones you can reach depends on your role, and you switch between them using the link in the page footer.
45Open the portal in a browser at your agency's Claude for Government address followed by `/gateway`. Which views you can reach depends on your role, and you switch between them using the link in the page footer.
10246
103| View | Who has it | What it's for |
104| - | - | - |
105| [**Tenant**](https://claude.com/docs/government/tenant-admin/overview.md) | Tenant administrators | Creating organizations, configuring identity and access (single sign-on, provisioning, and routing rules), distributing seats, setting spend caps, and managing who else is a tenant administrator. |
106| [**Organization admin**](https://claude.com/docs/government/org-admin/overview.md) | Organization owners and tenant administrators | Managing users and seats, setting usage tiers, viewing analytics, and configuring organization-level settings. |
107| [**Account**](https://claude.com/docs/government/account/overview.md) | Everyone | Viewing your own profile, checking your usage limits, and managing where you're signed in. |
47* [**Tenant**](https://claude.com/docs/government/tenant-admin/overview.md): tenant administrators
48* [**Organization admin**](https://claude.com/docs/government/org-admin/overview.md): organization owners and tenant administrators
49* [**Account**](https://claude.com/docs/government/account/overview.md): everyone
10850
109When you sign in, you land on the most relevant view for you. Organization owners land on the organization admin view, and everyone else lands on their account view. This includes tenant administrators who are not also an organization owner; they start on their account view and can use the **Switch to admin view** link in the page footer, and from there switch to the tenant view.
51Organization owners land on the organization admin view, and members with no administrative role land on their account view. Tenant administrators reach the tenant view from the **Switch to tenant view** link in the organization admin view's footer.
11052
111### A note on tenant administrators
53Being a [tenant administrator](https://claude.com/docs/government/tenant-admin/admins.md#how-tenant-admin-access-works) is separate from the role you hold inside an organization.
11254
113Being a tenant administrator is separate from the role you hold inside an organization. Roles (User, Owner, and Primary Owner) control what you can do within a single organization, while tenant administrator status is granted by adding someone to the tenant's **Admins** list and controls access to the settings that sit above every organization. The two are independent: an organization owner is not automatically a tenant administrator, and a tenant administrator does not automatically hold any particular role inside any organization.
114
115> **For tenant administrators:** Because the tenant sits above every organization, you can also open the organization admin view and act on behalf of any organization in the tenant, even ones you don't belong to. When the tenant has more than one organization, an organization switcher appears at the top of the admin view so you can choose which one you're managing.
116
11755## How people get access
11856
119Users reach your deployment in one of two ways, both of which are configured by a tenant administrator on the [Identity and access](https://claude.com/docs/government/tenant-admin/identity-and-access.md) page:
120
121* **Single sign-on.** The user enters their agency email address and is redirected to your identity provider (for example, Microsoft Entra, Okta, or ADFS). When they return authenticated, Claude for Government evaluates your tenant's routing rules to decide which organization they belong in.
122* **Directory provisioning.** If your identity provider supports SCIM, which is a standard way for directory systems to keep accounts in sync with other applications, you can connect it so that your directory pushes users and group memberships to Claude for Government automatically. Routing rules then place each provisioned user in an organization based on their group membership.
123
124A new person who does not match any rule cannot sign in until a rule is added that covers them. Routing rules are also re-evaluated each time an existing member signs in, so a rule change can move someone to a different organization the next time they sign in.
125
126## Where to go next
127
128* Read [**Tenant administration**](https://claude.com/docs/government/tenant-admin/overview.md) if you're a tenant administrator managing the overall deployment.
129* Read [**Organization administration**](https://claude.com/docs/government/org-admin/overview.md) if you're an owner managing a single organization.
130* Read [**Your account**](https://claude.com/docs/government/account/overview.md) if you want to understand your own profile, usage, and sessions.
57A tenant administrator connects your agency's [single sign-on](https://claude.com/docs/government/tenant-admin/identity-and-access.md#single-sign-on) and, optionally, [directory provisioning (SCIM)](https://claude.com/docs/government/tenant-admin/identity-and-access.md#scim-provisioning) on the [Identity and access](https://claude.com/docs/government/tenant-admin/identity-and-access.md) page. [Routing rules](https://claude.com/docs/government/tenant-admin/identity-and-access.md#routing-rules) then decide which organization each person joins. A new person who does not match any rule cannot sign in until a rule is added that covers them. A rule change can also move people who already have an account, as described in [When rules move people](https://claude.com/docs/government/tenant-admin/identity-and-access.md#when-rules-move-people).
13158
No line in this hunk matches that.