One read of Claude Documentationclaude-docs-20261106T200706Z
10 pages moved out of 281 read.
Pages moved
10
significant first
Pages read
281
in this capture
Captured
20:07 UTC
Corpus hash
2a48b4c4d78f
corpus-hash
What this read moved
1-10 of 10government/connectors/overview Changed · +50 / -60 lines
### Change or stop an inherited connector ### Server address and authentication ### Register an app for sign-in ### Tool discovery ### Products and tool policy ### Connection to server failed ## The Connectors card ### Step 1: Server ### Step 2: Discover tools ### Step 3: Policy & scope
from line 1
11# Connectors
22
3> Add Model Context Protocol servers for your own systems, choose which Claude products receive each one, and set which of their tools are available to members.
3> Connectors let tenant administrators and organization owners add their agency's MCP servers: who gets them, authentication, OAuth redirect URIs, tool policy.
44
55> **Who this is for:** Tenant administrators and organization owners who want Claude to reach their agency's own systems (for example, an internal search service or a ticketing tool) from Claude Desktop and other Claude products.
66
7Use this page to add Model Context Protocol servers for your own systems, choose which Claude products receive each one, and set which of their tools are available to members.
7Use this page to add Model Context Protocol (MCP) servers for your own systems, choose which Claude products receive each one, and set which of their tools are available to members.
88
9A **connector** is a link between Claude and an external service. The service runs a Model Context Protocol (MCP) server, which is a standard way for a service to publish a set of tools that Claude can call. You add the server once here, and Claude for Government delivers it to the products you select.
9A **connector** is a link between Claude and an external service. The service, your agency's own or a vendor's, runs an MCP server, which is a standard way for a service to publish a set of tools that Claude can call. You add the server once here, and Claude for Government delivers it to the products you select.
1010
11<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-07-connectors-and-plugins.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=43f78d15928eea46d27229f8dbc04db6" aria-label="Video walkthrough: Connectors and plugins" />
12
13Video: Connectors and plugins (2 min 8 s). Narrated with an AI-generated voice, with on-screen captions.
14
15> [accordion] Transcript
11> [!NOTE]
1612>
17> A connector lets Claude reach another service, such as Microsoft 365 or a system of your own. A plugin packages skills and commands for Claude Desktop.
13> These cases are covered on other pages:
1814>
19> Microsoft 365 setup starts in Microsoft Entra. An Entra administrator registers an application, approves its Microsoft Graph permissions, and sends you two values, the tenant ID and the client ID.
20>
21> On Config, under Integrations, expand Microsoft 365. Paste the Tenant ID and the Client ID, keep Azure cloud on Commercial unless your Microsoft tenant is in GCC High or DoD. Check that Access matches what Entra approved, and save.
22>
23> Members then connect Microsoft 365 in Claude Desktop with their own work account, and Claude reaches only what each member can already open.
24>
25> For a system of your own, open Add connector on the Connectors card. Name it, enter the server's address, and choose how Claude authenticates, for example a shared secret or member sign-in. Select Next.
26>
27> Discover tools asks the server which tools it offers. If the server cannot be reached from your browser, add tool names by hand on the next step.
28>
29> Under Apply to, choose the products that receive it, here Claude Desktop only. Under Tool policy, switch off any tool you do not want, then save the connector. Members are still asked before Claude uses an allowed tool.
30>
31> On the Plugins card, select Add plugins and drop a zip file. The preview shows its name and version. Choose Auto-install for everyone, or Members choose, then add it.
32>
33> You do not need to push anything. Claude Desktop picks up the connector and the plugin when it next checks for changes. Members find plugins under Customize, Plugins.
15> * **The Microsoft 365 connector**: see [Set up the Microsoft 365 connector](https://claude.com/docs/government/connectors/microsoft-365.md)
16> * **Plugins**: see [Manage plugins and connectors](https://claude.com/docs/government/config/plugins-and-connectors.md)
3417
35## The Connectors card
18<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-07-connectors-and-plugins.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=43f78d15928eea46d27229f8dbc04db6" aria-label="Video walkthrough: Connectors and plugins" />
3619
37The **Connectors** card appears on your [tenant](https://claude.com/docs/government/tenant-admin/configuration.md) or [organization](https://claude.com/docs/government/org-admin/configuration.md) Config page alongside the built-in connector cards, and on the Config page for each [directory group](https://claude.com/docs/government/config/overview.md#group-specific-settings). It lists the connectors added at the level you are viewing and the connectors that level inherits, with each one's name, address, the products it applies to, and a summary of how many of its tools are allowed. Click **Add connector** to open the wizard, or click the edit icon next to a connector added at this level to change it.
20Video: Connectors and plugins (2 min 8 s). Narrated with an AI-generated voice, with on-screen captions.
3821
39An inherited connector has a badge that says where it comes from, such as **Inherited from your tenant** or **Inherited from your organization**, in place of the edit and remove controls. To change an inherited connector for the members at your level, click **Add connector** and create one with the same name. The inherited connector's details and stored secret are not copied, so you enter the server address and authentication again. Your entry then replaces the inherited one in the list and takes priority over it, as described under [Who receives a connector](#who-receives-a-connector).
22[Transcript](https://claude.com/docs/government/video-walkthroughs.md#connectors-and-plugins)
4023
4124## Who receives a connector
4225
43Who receives a connector depends on where you add it:
26To see or add connectors, go to **Settings > Config** and open the **Connectors** card, under **Integrations**. A connector reaches the people whose settings you are editing when you add it: everyone in the [tenant](https://claude.com/docs/government/tenant-admin/configuration.md), everyone in an [organization](https://claude.com/docs/government/org-admin/configuration.md), or the members of one directory group, as described under [Group-specific settings](https://claude.com/docs/government/config/overview.md#group-specific-settings). In every case it is delivered only to the products you select, with the tool policy you set.
4427
45* On the tenant Config page, it reaches the members of every organization in the tenant.
46* On an organization's Config page, it reaches every member of that organization.
47* On the Config page for a [directory group](https://claude.com/docs/government/config/overview.md#group-specific-settings), it reaches that group's members: in every organization when you open the group from the tenant Config page (a tenant-wide group setting), or only in one organization when you open the group from that organization's Config page (an organization group setting).
28A connector added for a group does not always reach every member of the group. Only one group's settings, connectors included, apply to each person, as described under [When someone belongs to more than one group](https://claude.com/docs/government/config/overview.md#when-someone-belongs-to-more-than-one-group).
4829
49In every case it is delivered only to the products you select, with the tool policy you set.
30When the same connector name is added at more than one level, each member receives only the entry from the [most specific level](https://claude.com/docs/government/config/overview.md#how-settings-are-applied) that applies to them. That entry replaces the others as a whole, including its address, authentication, products, and tool policy.
5031
51When the same connector name is added at more than one level, each member receives only the entry from the most specific level that applies to them: the organization's group settings first, then the organization, then the tenant-wide group settings, then the tenant. That entry replaces the others as a whole, including its address, authentication, products, and tool policy. You cannot remove a connector inherited from a level above, but you can stop it from reaching the members at your level by adding one with the same name and selecting no products under **Apply to**.
32### Change or stop an inherited connector
5233
53A connector added for a group does not always reach every member of the group. Someone who belongs to more than one directory group receives group settings, connectors included, from only one of them: their [highest-priority group](https://claude.com/docs/government/config/overview.md#when-someone-belongs-to-more-than-one-group) that has any configuration. Adding a group's first connector or deleting its last one can therefore change which group, and so which group settings, apply to some members. The group's Config page shows a note when this could happen. To check which group applies to a particular member, use the person lookup described under [Comparing settings across levels](https://claude.com/docs/government/config/overview.md#comparing-settings-across-levels).
34Unless a level above has [locked](https://claude.com/docs/government/config/overview.md#locks) the **Connectors** card, you can change an inherited connector for the members at your level: click **Add connector** and create one with the same name. The inherited connector's details and stored secret are not copied, so you enter the server address, authentication, and tool policy again. You cannot remove a connector inherited from a level above, but in the same way you can stop it from reaching the members at your level: add one with the same name and select no products under **Apply to**.
5435
5536## Adding a connector
5637
57The **Add connector** button opens a three-step wizard.
38Go to **Settings > Config**, open the **Connectors** card, and click **Add connector**. On the tenant Config page, you first choose whether organizations **May set their own value** or **Must use this value**, which stops organizations and groups from adding connectors or replacing yours.
5839
59### Step 1: Server
40### Server address and authentication
6041
61Enter the details of the MCP server.
62
63* **Name** is a short identifier for the connector. It must be lowercase letters, digits, hyphens, or underscores.
64* **Server URL** is the address of the server's MCP endpoint. It must begin with `https://`.
42* **Name** is a short identifier for the connector. It must be letters a to z in either case, digits, hyphens, or underscores. Claude Desktop shows members [the name](https://claude.com/docs/third-party/claude-desktop/configuration.md#managedmcpservers) with the capital letters you type. If you add a connector with a name already used at your level, even with different capital letters, the new connector replaces that one, tool policy included.
43* **Server URL** is the address of the server's MCP endpoint. It must begin with `https://`. Enter the address the server answers on, not one that redirects to it. Claude Desktop [connects to it directly from each member's device](https://claude.com/docs/government/security/security-and-data-handling.md#connectors), so the server, and its sign-in provider if it uses OAuth, must be reachable from those devices. You do not need to ask Anthropic to allow either address.
6544* **Transport** selects how Claude talks to the server. Choose HTTP or SSE to match what your server supports.
66* **Authentication** selects how Claude proves who it is to the server. **None** sends no credentials. **Header (shared secret)** sends a fixed header (for example, an authorization token) with every request; the value is stored securely and shown as `••••` after you save. **OAuth (members sign in)** has each member sign in on first use, and their tokens stay on their own machine. **OAuth (pre-registered app)** also has each member sign in, through an app you register with the server's sign-in provider ahead of time.
45* **Authentication** selects how Claude proves who it is to the server:
46 * **None** is for a server that needs no sign-in: it sends no credentials. If the server asks for sign-in anyway, Claude Desktop [lets each member sign in](https://claude.com/docs/third-party/claude-desktop/extensions.md#oauth-sign-in).
47 * **Header (shared secret)** sends a fixed header (for example, an authorization token) with every request; the value is stored securely and shown as `••••` after you save, and each member's app receives it.
48 * **OAuth (members sign in)** has each member sign in on first use, and their tokens stay on their own machine. Choose it when the server's sign-in provider lets apps register themselves (dynamic client registration).
49 * **OAuth (pre-registered app)** also has each member sign in, through an app you register with the server's sign-in provider ahead of time. Choose it when the provider has you create an app and copy its client ID.
6750
68For **OAuth (pre-registered app)**, enter the **Client ID** your provider issued when you registered the app. A single-tenant Microsoft Entra app also needs its **Tenant ID** and the **Scope** the app requests. Enter the scope that your server's own API expects (for example, an `api://` scope for an app registered in your tenant), because Microsoft Graph scopes such as `Mail.Read` would give the connector's server access to members' Microsoft 365 data. Neither OAuth option stores a secret.
51Neither OAuth option stores a secret. If the server's sign-in provider requires a client secret, members can't connect to that server.
6952
70**OAuth (pre-registered app)** also has two optional fields:
53When you choose either OAuth option, a confirmation checkbox appears on the final step asking you to confirm that the server address is exactly the one you intend, because members are sent to a sign-in page that the server chooses. When sign-in happens somewhere other than the server itself, for example when you set a tenant ID for a Microsoft Entra app, the checkbox names both that sign-in address and the server address.
7154
72* **Callback port**: if your sign-in provider requires the exact port in the app's registered redirect URI, enter that port
73* **Callback host**: if the app's registered redirect URI uses `localhost` rather than `127.0.0.1`, select **localhost**
55### Register an app for sign-in
7456
75When you choose either OAuth option, a confirmation checkbox appears on the final step asking you to confirm that the server address is exactly the one you intend, because members are sent to a sign-in page that the server chooses. When sign-in happens somewhere other than the server itself, for example when you set a tenant ID for a Microsoft Entra app, the checkbox names both that sign-in address and the server address.
57For **OAuth (pre-registered app)**, add Claude Desktop's [redirect URI](https://claude.com/docs/third-party/claude-desktop/extensions.md#oauth-sign-in), `http://127.0.0.1:53280/callback`, to the app's registration with your sign-in provider. If the registration uses another port or `localhost`, set **Callback port** or **Callback host** in the wizard to match. Have the app's client ID ready, and for a single-tenant Microsoft Entra app its tenant ID and scope as well.
7658
77### Step 2: Discover tools
59For the Claude Code command-line tool, set **Callback port** to the port you registered for Claude Desktop. Also add `http://localhost:PORT/callback`, with that port, to the registration. A connector with a tenant ID is not delivered to the command-line tool.
7860
79This step tries to list the tools the server offers so that you can set policy on the next step. Discovery runs from your own browser and is best-effort; many servers cannot be reached this way (for example, because they require authentication or are on a private network), and you can always add tools by name on the next step instead.
61Enter the scope that your server's own API expects (for example, an `api://` scope for an app registered in your tenant), because Microsoft Graph scopes such as `Mail.Read` would give the connector's server access to members' Microsoft 365 data.
8062
81Click **Discover tools** to run the probe. If the server answers, the tools it advertises are listed. If the server asks for sign-in, a **Sign in to discover** option appears: confirm the sign-in host, sign in through the popup, and the probe runs again with that one-time credential. The credential is used once in your browser for this probe and is never stored; it is separate from the **Authentication** choice on the Server step, which controls how members authenticate later.
63### Tool discovery
8264
83The **Sign in to discover** option does not appear when you choose **OAuth (pre-registered app)**, because this probe does not sign in with the app you registered. Add the tools by name on the next step.
65The wizard tries to list the tools the server offers, so that you can set policy on them. Discovery runs from your own browser and is best-effort; many servers cannot be reached this way (for example, because they require authentication or are on a private network), and you can always add tools by name on the next step instead.
8466
85### Step 3: Policy & scope
67Discovery can ask you to sign in to the server. The credential is used once in your browser for this probe and is never stored; it is separate from the **Authentication** choice on the Server step, which controls how members authenticate later.
8668
87Choose which products receive this connector and which of its tools are available.
69### Products and tool policy
8870
89Under **Apply to**, tick the products that should receive this connector. A connector with no products ticked is saved but delivered nowhere, which is a way to pause it. A connector that uses OAuth cannot be applied to Microsoft 365, because per-user sign-in is not available there. A connector with any tool switched off in the table below also cannot be applied to Microsoft 365, and the checkbox is disabled with a **needs every tool on** note until every tool is on. A connector that uses **OAuth (pre-registered app)** with a **Tenant ID** is not delivered to the Claude Code command-line tool, and its checkbox shows a **not delivered to the Claude Code command-line tool** note.
71Under **Apply to**, tick the products that should receive this connector. **Microsoft 365** is the [Claude for Microsoft 365 add-in](https://claude.com/docs/government/deploy-microsoft-365/configure.md#before-you-begin), which cannot receive a connector that uses OAuth or that has any tool switched off.
9072
91Under **Tool policy**, the table lists the tools found during discovery with an on/off switch for each. **Refresh tools** probes the server again and fills in any tools that are new since you last looked, keeping the switches you have already set. **Add tool** lets you type a tool name by hand when discovery could not reach the server.
73Under **Tool policy**, switch each of the server's tools on or off, or leave it unlisted. On Claude Desktop, that tool policy shapes what members experience:
9274
93On Claude Desktop, a tool you switch off is blocked, a tool you switch on is available and each member still approves its use, and a tool that is not listed at all is left to the member to enable or disable. You cannot apply this connector to Microsoft 365 while any tool in this table is switched off. If you are editing a connector that already applies to Microsoft 365 and you switch a tool off, a warning tells you that saving will remove it from Microsoft 365.
75* A tool you switch off is blocked, so Claude cannot use it.
76* A tool you switch on is available and asks the member on every use, and members are not offered a lasting approval for it. Its permission control is locked, and hovering over it shows **Permission set by your admin**.
77* A tool you do not list is left to the member to turn on or off, and its approval prompts follow the member's own choices, which can include lasting approval. To return a listed tool to each member's control, remove its row.
9478
95Click **Save** to create the connector. It appears in the **Connectors** card and is delivered to the products you ticked.
79A saved connector reaches members as described under [When changes take effect](https://claude.com/docs/government/config/overview.md#when-changes-take-effect).
9680
81### Connection to server failed
82
83If **Connect** in Claude Desktop shows "Connection to server failed. You can try again.", check first that the device can reach the server's address, that the app you registered lists the redirect URI, and that no other program is using the callback port. When the provider doesn't list the redirect URI, its own error page opens in the member's browser. In the other two cases the member's [`main.log`](https://claude.com/docs/government/deploy-desktop/configure#troubleshooting) records the reason. [How OAuth sign-in works](https://claude.com/docs/third-party/claude-desktop/extensions.md#how-oauth-sign-in-works) lists other causes.
84
9785## Editing and removing a connector
9886
99Click the edit icon next to a connector in the card to open the same wizard with its current values filled in. Changing the authentication method clears any stored secret and the app details saved for **OAuth (pre-registered app)**. Click the remove button next to a connector to delete it; it is withdrawn from every product at the next refresh. If you delete a connector that takes priority over an inherited connector with the same name, the inherited connector applies again from that refresh.
87To change a connector, edit it on the **Connectors** card. Changing the authentication method clears any stored secret and the app details saved for **OAuth (pre-registered app)**.
88
89Click the remove button next to a connector to delete it; it is withdrawn from every product [when the change takes effect](https://claude.com/docs/government/config/overview.md#when-changes-take-effect). If you delete a connector that takes priority over an inherited connector with the same name, the inherited connector applies again.
10090
government/org-admin/provisioning Changed · +8 / -8 lines
from line 15
1515
1616## Group to seat tier
1717
18To add a mapping, choose a group and a tier and click **Add**. Members of the group are moved to that tier, existing users included. To change a group's tier, click **Remove** on its mapping and add a new one. Each group can be mapped to at most one tier, and you can only select tiers that are available to this organization (either an Anthropic-managed tier you have been allocated or a self-managed tier you created on the [Tiers](https://claude.com/docs/government/org-admin/seat-tiers.md#creating-a-self-managed-tier) page).
18To add a mapping, choose a group and a tier and click **Add**. Members of the group are moved to that tier, existing users included. To change a group's tier, click **Remove** on its mapping and add a new one. Each group can be mapped to at most one tier.
1919
20* **Someone who leaves a mapped group** keeps the tier, with its models and spend limits, until another mapping or an owner moves them. On a tier with a seat limit, a [reconciliation](#how-mappings-are-applied) can move them too.
21* **Mapping a group to a tier with a [seat limit](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically)** can move other people off it. At a reconciliation, provisioned users on it who are in no mapped group can be moved to another tier with a free seat. If none is free, they stay.
20* **Someone who leaves a mapped group, or whose group's mapping is removed,** keeps the tier, with its models and spend limits, until another mapping or an owner moves them. On a tier with a seat limit, a [reconciliation](#how-mappings-are-applied) can move them too.
21* **Mapping a group to a tier with a seat limit** can move other people off it. At a reconciliation, provisioned users on it who are in no mapped group can be moved to the tier in [step 3](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically) if it comes before theirs. On the tier marked **New members start here**, they stay.
2222
2323If no groups have appeared at all, ask your tenant administrator to assign groups to the Claude for Government application in your identity provider and run a provisioning sync first.
2424
2525## Group to role
2626
27Map a directory group to **User** or **Owner**, and members of that group receive that role when they are provisioned. You cannot map a group to Primary Owner; that role must always be granted manually on the [Users](https://claude.com/docs/government/org-admin/users.md) page.
27Make your first role mapping a group that holds all your Owners, mapped to **Owner**. An Owner left out of it can lose access to this portal. You cannot map a group to Primary Owner; grant that role on the [Users](https://claude.com/docs/government/org-admin/users.md) page.
2828
29Once this organization has any group-to-role mapping, every provisioned member except a Primary Owner gets their mapped role, or **User** if none of their groups is mapped. Map your Owners' group first, so that they keep access to this portal.
29While this organization has no group-to-role mapping, members keep their roles unless a rule [moves them to another organization](https://claude.com/docs/government/tenant-admin/identity-and-access.md#when-rules-move-people). Once it has one, every member [linked to your directory](https://claude.com/docs/government/tenant-admin/identity-and-access.md#existing-accounts-when-you-connect-scim) except a Primary Owner gets their mapped role, or **User** if none of their groups is mapped. So you don't need to map any group to **User**.
3030
3131## How mappings are applied
3232
3333Each push from your identity provider is applied to your user list by a reconciliation pass.
3434
35* **After a mapping change.** Adding or removing a mapping starts a full reconciliation, so existing users are re-evaluated against the new mapping without waiting for your identity provider's next sync. In a very large directory, a full reconciliation can take hours.
36* **Several mapped groups.** When a provisioned user belongs to several groups mapped to a seat tier, the one highest in your tenant's [group priority](https://claude.com/docs/government/tenant-admin/identity-and-access.md#directory-groups) decides. Role mappings follow a fixed order, so avoid mapping groups that share members to different roles.
35* **After a mapping change.** Adding or removing a mapping starts a full reconciliation, so existing users are re-evaluated without waiting for your identity provider's next sync. In a very large directory, it can take hours.
36* **Several mapped groups.** When a provisioned user belongs to several groups mapped to a seat tier, the one highest in your tenant's [group priority](https://claude.com/docs/government/tenant-admin/identity-and-access.md#directory-groups) decides. For roles, an order you can't see or change decides, and **User** can win over **Owner**. So don't map a group that includes your Owners, such as an all-staff group, to **User**.
3737* **No mapped group.** See [How seats are assigned automatically](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically).
38* **No free seats.** If a user's mapped tier has no free seats, provisioning doesn't add a new person yet, and an existing member keeps their current seat tier or stays **Unassigned**. Increasing the tier's allocation places them, up to the new limit.
38* **No free seats.** If a new person's mapped or marked tier is full, provisioning doesn't add them yet. An existing member whose mapped tier is full keeps their current tier or stays **Unassigned**. They are tried again at each full reconciliation, which changing seat allocations or mappings starts, and when your directory updates their entry.
3939
4040## What your directory controls
4141
government/org-admin/seat-tiers Changed · +26 / -34 lines
## The tier list ## Anthropic-managed versus self-managed tiers ## Things to know
from line 1
11# Seat tiers
22
3> Use this page to see the models and spend limits attached to each tier and, when permitted, to create and edit self-managed tiers.
3> Seat tiers set which Claude models a user can access and how much they can spend. Organization owners create and manage their own seat tiers.
44
55> **Who this is for:** Organization owners who need to review the seat tiers available to their organization or define their own.
66
7Use this page to see the models and spend limits attached to each tier and, when permitted, to create and edit self-managed tiers.
7A **seat tier** bundles together which Claude models a user may access and how much they may spend in a given period. Every user sits on exactly one tier (or is unassigned), and the tier they hold controls their day-to-day limits. The **Tiers** page lists every tier available to your organization. To open it, go to **People > Tiers** in the [organization admin portal](https://claude.com/docs/government/org-admin/overview.md#who-can-access-it). Tenant administrators reach that portal through **Switch to org view** in the tenant view's footer.
88
9A **seat tier** bundles together which Claude models a user may access and how much they may spend in a given period. Every user sits on exactly one tier (or is unassigned), and the tier they hold controls their day-to-day limits. The **Tiers** page lists every tier available to your organization.
9> [!NOTE]
10>
11> These tasks are covered on other pages:
12>
13> * **Put a user on a tier**: see [Assigning a seat tier](https://claude.com/docs/government/org-admin/users.md#assigning-a-seat-tier)
14> * **Turn a Claude product on or off**: see [Product availability](https://claude.com/docs/government/config/settings.md#product-availability)
1015
11## The tier list
16The tiers your organization creates are **self-managed tiers**. They draw from the credits in the [billing account](https://claude.com/docs/government/org-admin/billing.md) your organization spends from, so requests from people on them are refused while the account has no credits or your organization has reached a spend cap. They have no seat limit unless one is set.
1217
13Tiers are listed with Anthropic-managed tiers first, followed by your organization's self-managed tiers. Each entry shows the tier's name, how many users are currently on it, and the seat limit if one applies. Clicking any tier opens its detail page.
18> [!NOTE]
19>
20> **Anthropic-managed tiers.** If your agency buys seats, Anthropic sets up your tiers, and you don't need to create any. You can't delete an Anthropic-managed tier or change what it allows, and its spend limits aren't shown. To start new members on one, go to **People > Tiers**, open the tier, select [**New members start here**](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically), and click **Save**. These tiers don't draw from credits, so people on them keep working while the account has none.
1421
15## Anthropic-managed versus self-managed tiers
16
17**Anthropic-managed tiers** are defined by Anthropic and allocated to you through your tenant's billing account. On the detail page you can see the tier's **Allowed models**, its **Default model**, and whether **Always start with the default model** is on. The spend limits aren't shown, and you can't delete the tier or change what it allows. These tiers are paid for as seats rather than through credit drawdown, so their per-user spend limits are an internal detail that Anthropic manages on your behalf.
18
19**Self-managed tiers** are created by your organization. They draw from the billing account your organization spends from instead of a fixed seat count, and you have full control over their settings. A self-managed tier may or may not have a seat limit, depending on how it was allocated; when it has no limit, you can place as many users on it as you wish and the account's balance and any spend cap set on your organization are the effective constraint.
20
2122## Creating a self-managed tier
2223
2324You can create, edit, and delete self-managed tiers only if your tenant has [allowed organizations to manage their own seat tiers](https://claude.com/docs/government/config/settings.md#let-organizations-manage-their-own-seat-tiers). Go to **People > Tiers**, click **New seat tier**, and fill in the form. If you don't see the button, a tenant administrator can turn on that setting. If it is already on, contact your Anthropic representative.
2425
25* **Name** sets what the tier is called, for example *Analyst* or *Reviewer*. Names must be unique within your organization, and cannot duplicate the name of any Anthropic-managed tier.
26* **Five-hour spend limit** sets the most each user on this tier can spend in any rolling 5-hour window, expressed in dollars. When a user reaches this amount, further requests are refused until the window rolls forward. Set it to zero to allow no usage at all.
27* **Seven-day spend limit** does the same for a rolling 7-day window. Both limits apply at the same time, so whichever is reached first stops the user.
28* **Allowed models** controls which Claude models users on this tier may use. If you leave it empty, users on the tier have no model access regardless of their spend limits.
26> [!WARNING]
27>
28> Make sure your [billing account](https://claude.com/docs/government/org-admin/billing.md) has credits before anyone is placed on the tier, or their requests are refused.
29
30* **Five-hour spend limit** sets how much each user on this tier can spend in a 5-hour window, expressed in dollars. When a user reaches this amount, further requests are refused until the limit [resets](https://claude.com/docs/government/account/usage.md#reading-the-reset-times).
31* **Seven-day spend limit** does the same for a 7-day window. Both limits apply at the same time, so whichever is reached first stops the user.
32* **Allowed models** controls which [Claude models](https://claude.com/docs/government/desktop/models.md) users on this tier may use. If you leave it empty, users on the tier have no model access regardless of their spend limits.
2933* **Default model** sets the model that new chats, tasks, and Code sessions in Claude Desktop start on, chosen from the tier's allowed models. It applies to users who haven't picked a model or effort level in the model picker.
3034* Select **Always start with the default model** to start every new chat, task, and Code session on the default model. Requires a **Default model** and Claude Desktop 2.110.0 or later.
31* **Sort order** is a number that controls the order in which a seat is automatically chosen for a newly provisioned user (lowest number is tried first). If two tiers share the same sort order they are ordered consistently, but it is clearer to give each tier a distinct value.
32* **New members start here** makes this the tier that people start on when they join your organization, as described under [How seats are assigned automatically](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically). Turning it on here turns it off for any other tier.
35* **New members start here** makes this the tier that people start on when they join your organization, as described under [How seats are assigned automatically](https://claude.com/docs/government/org-admin/seats.md#how-seats-are-assigned-automatically). Turning it on here turns it off for any other tier. On a tier with a seat limit and a mapped group, turning it off can move provisioned users who are in no mapped group [to another tier](https://claude.com/docs/government/org-admin/provisioning.md#group-to-seat-tier).
3336
34An organization may create up to 50 self-managed tiers.
35
3637## Viewing and editing a tier
3738
38A tier's detail page shows its current values along with an **Allowed models** section that groups the permitted models by family.
39Go to **People > Tiers**, open a self-managed tier, and use its **Edit** form.
3940
40> [!NOTE]
41>
42> The **Edit** form and **Delete** button only appear on self-managed tiers.
41* Changes to spend limits and allowed models take effect immediately for every user on the tier: if you lower the spend limit, a user who is already over the new limit will be blocked on their next request until the limit resets, and if you remove a model from **Allowed models** it becomes unavailable to every user on the tier straight away.
42* Changes to **Default model** and **Always start with the default model** reach users when Claude Desktop next [refreshes its configuration](https://claude.com/docs/government/config/overview.md#when-changes-take-effect), and a new default appears the next time they start Claude Desktop. When you set or change a tier's **Default model**, Claude Desktop prompts users on that tier who have the app open [to restart](https://claude.com/docs/government/config/settings.md#restart-deadline-for-configuration-changes). To avoid the prompt, set a tier's **Default model** before its users first open Claude Desktop.
4343
44For a self-managed tier the **Edit** form lets you update any of the fields above. Changes to spend limits and allowed models take effect immediately for every user on the tier: if you lower the spend limit, a user who is already over the new limit will be blocked on their next request until their window rolls forward, and if you remove a model from the allowlist it becomes unavailable to every user on the tier straight away. Changes to **Default model** and **Always start with the default model** reach users when Claude Desktop next [refreshes its configuration](https://claude.com/docs/government/config/overview.md#when-changes-take-effect), and a new default appears the next time they start Claude Desktop.
44If a banner that begins **Anthropic has provided default seat tiers** appears in the organization admin portal, Anthropic has set up a self-managed seat tier for your organization to review. Click **Review seat tiers**, then adjust the tier in the **Edit** form and click **Save**, or click **Keep these values**.
4545
46When you set or change a tier's **Default model**, Claude Desktop prompts users on that tier who have the app open to restart. Claude Desktop requires the restart once the [**Restart deadline for configuration changes**](https://claude.com/docs/government/config/settings.md#restart-deadline-for-configuration-changes) passes, 24 hours by default. If you also select **Always start with the default model**, those users start new chats on the first model in their model picker until they restart. To avoid the prompt, set a tier's **Default model** before its users first open Claude Desktop.
47
4846## Deleting a tier
4947
50The **Delete** button removes a self-managed tier entirely. Deletion is permanent and cannot be undone from this portal.
48Go to **People > Tiers**, open a self-managed tier, and click **Delete** to remove it entirely. Deletion is permanent.
5149
52You can only delete a tier that nothing references. If any users are still assigned to it, any API keys are bound to it, or any group mapping on the [Group mappings](https://claude.com/docs/government/org-admin/provisioning.md) page points at it, the delete is refused with a message telling you so. Reassign or remove those references first, then delete the tier.
53
54## Things to know
55
56* The spend limits are per user, not per tier. Ten users on a tier with a \$20 seven-day limit can together spend up to \$200 from the billing account over seven days.
57* Moving a user between tiers does not reset their usage counters. A user who has spent \$15 in the current 5-hour window carries that spend with them, and it is measured against the new tier's limit on their next request.
58* Users choose among a tier's allowed models in the Claude Desktop model picker, described in [Models in Claude Desktop](https://claude.com/docs/government/desktop/models.md). Some models also offer a 1M context window, which Anthropic sets per model and which is not part of the tier.
50If any users are still assigned to it, or any group mapping on the [Group mappings](https://claude.com/docs/government/org-admin/provisioning.md) page points at it, the delete is refused. Reassign or remove those references first, then delete the tier.
5951
government/video-walkthroughs Changed · +13 / -13 lines
from line 14
1414
1515How a tenant, its organizations, and their users fit together, how administrators sign in to the web portal, and how to move between the admin, tenant, and account views. Read more: [The three views](https://claude.com/docs/government/overview.md#the-three-views).
1616
17<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" />
17<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/mGbOjjHMKV3LYuqi/images/government/videos/admin-01-finding-your-way-around-v2.mp4?fit=max&auto=format&n=mGbOjjHMKV3LYuqi&q=85&s=4aaba8c318c1a044b343874cc64c95c3" aria-label="Video walkthrough: Finding your way around" />
1818
19Video: Finding your way around (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
19Video: Finding your way around (2 min 24 s). Narrated with an AI-generated voice, with on-screen captions.
2020
2121> [accordion] Transcript
2222>
from line 24
2424>
2525> 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.
2626>
27> In a browser, open your agency's Claude for Government address and enter your work email.
27> In a browser, open your agency's Claude for Government address followed by /gateway, and enter your work email.
2828>
2929> Select Continue, and your agency's usual sign-in page opens.
3030>
from line 94
9494
9595Adding a sign-in routing rule that places new people in the right organization, adding an organization, and giving it seats. To send people to an organization by group, use a [provisioning rule](https://claude.com/docs/government/tenant-admin/identity-and-access.md#provisioning-rules-scim) rather than the identity provider group rule shown in the video. Read more: [Routing rules](https://claude.com/docs/government/tenant-admin/identity-and-access.md#routing-rules).
9696
97<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-03-organizations-seats-and-routing-rules.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=3b4fdf17a38f17ace0a31daff24dd678" aria-label="Video walkthrough: Organizations, seats, and routing rules" />
97<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gG0BlHWciPZj0Lhu/images/government/videos/admin-03-organizations-seats-and-routing-rules-v2.mp4?fit=max&auto=format&n=gG0BlHWciPZj0Lhu&q=85&s=c327b48633e8619e07ced55a9765ede5" aria-label="Video walkthrough: Organizations, seats, and routing rules" />
9898
9999Video: Organizations, seats, and routing rules (2 min 14 s). Narrated with an AI-generated voice, with on-screen captions.
100100
from line 120
120120>
121121> On Seats, the billing account shows its pool and the organizations it funds. Give Research Office seats and select Save. Its first seats also seat its Primary Owner, and the setup banner clears.
122122>
123> To send people to Research Office, add an identity provider group rule for them and drag it above the domain rule. Each person belongs to exactly one organization.
123> Each person belongs to exactly one organization.
124124
125125### Directory sync (SCIM) and group mappings
126126
127127Connecting SCIM provisioning, routing directory groups to organizations, and mapping groups to seat tiers and roles. Read more: [SCIM provisioning](https://claude.com/docs/government/tenant-admin/identity-and-access.md#scim-provisioning) and [Group mappings](https://claude.com/docs/government/org-admin/provisioning.md).
128128
129<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-04-directory-sync-scim-and-group-mappings.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=e254e02786c5f309b5c5c240c7752c4e" aria-label="Video walkthrough: Directory sync (SCIM) and group mappings" />
129<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gG0BlHWciPZj0Lhu/images/government/videos/admin-04-directory-sync-scim-and-group-mappings-v2.mp4?fit=max&auto=format&n=gG0BlHWciPZj0Lhu&q=85&s=44cfafd3709ce812b546449ea1dc0752" aria-label="Video walkthrough: Directory sync (SCIM) and group mappings" />
130130
131131Video: Directory sync (SCIM) and group mappings (2 min 3 s). Narrated with an AI-generated voice, with on-screen captions.
132132
from line 146
146146>
147147> Once a rule covers them, they are placed in its organization, and the list clears on its own.
148148>
149> In the organization's admin view, People now includes Group mappings. Map claude-users to a seat tier, here Standard, and claude-owners to the Owner role. Each change is applied right away.
149> In the organization's admin view, People now includes Group mappings. Map claude-users to a seat tier, here Standard, and claude-owners to the Owner role.
150150>
151151> On Users, the provisioned members now hold their mapped seat tier and role.
152152>
from line 156
156156
157157Checking the **Readiness** page, assigning seat tiers and roles on the **Users** page, and reviewing the **Tiers** page. Read more: [Organization administration](https://claude.com/docs/government/org-admin/overview.md).
158158
159<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-05-organization-owners-users-seat-tiers-and-readiness.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=d235ae566a0056c409a1b59b2a9623e7" aria-label="Video walkthrough: Organization owners: users, seat tiers, and Readiness" />
159<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/MtPmUtGcabx4sJAO/images/government/videos/admin-05-organization-owners-users-seat-tiers-and-readiness-v2.mp4?fit=max&auto=format&n=MtPmUtGcabx4sJAO&q=85&s=fbfcdaca92e3c17ff358af64f4f81ae5" aria-label="Video walkthrough: Organization owners: users, seat tiers, and Readiness" />
160160
161161Video: Organization owners: users, seat tiers, and Readiness (1 min 48 s). Narrated with an AI-generated voice, with on-screen captions.
162162
from line 174
174174>
175175> Roles are User, Owner, and Primary Owner. Keep at least two Primary Owners, so one can always promote a replacement. From Priya's Role dropdown, Marcus chooses Primary Owner.
176176>
177> Tiers lists the seat tiers available to your organization. Anthropic-managed tiers are read-only, and your tenant can let you create your own.
177> Tiers lists the seat tiers available to your organization, and your tenant can let you create your own.
178178>
179179> Model access comes from the seat tier, never from the role. Tenant administrator is separate from these roles. If directory groups set roles or tiers, change the group in your provider, because the group mappings overwrite edits made by hand.
180180
from line 182
182182
183183Editing settings on the **Config** page for an organization or for one directory group, turning on web search, reviewing the session idle timeout, and locking a value for every organization from the tenant. Read more: [How Config works](https://claude.com/docs/government/config/overview.md).
184184
185<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-06-config-essentials.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=8624805f501e6ca7e01e12e6e94602ab" aria-label="Video walkthrough: Config essentials" />
185<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/QW2rDqtpaxS9YU5m/images/government/videos/admin-06-config-essentials-v2.mp4?fit=max&auto=format&n=QW2rDqtpaxS9YU5m&q=85&s=96c86f606126bba3b006c1950d4fa19d" aria-label="Video walkthrough: Config essentials" />
186186
187187Video: Config essentials (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
188188
from line 198
198198>
199199> Under Integrations, Web search is off by default. Turning it on asks you to acknowledge how search works. Require approval for each search stays on, so members approve every search.
200200>
201> Under Sessions and access, Session idle timeout signs out inactive members after 24 hours by default. Lower levels can only shorten it, and lowering it applies from the next sign-in.
201> Under Sessions and access, Session idle timeout signs out inactive members after 24 hours by default. Lower levels can only shorten it.
202202>
203203> In the tenant view, open the same page and set the Claude Desktop banner for everyone. Choose Must use this value, open Preview impact, then save. Every organization now uses this value.
204204>
205205> Back in the organization's Config, the banner shows Locked by your tenant and cannot be changed there.
206206>
207> You do not need to push anything. Claude Desktop checks for changes at launch and about every 10 minutes while it runs, or every 30 minutes on older versions, and prompts members to relaunch when something changed.
207> You do not need to push anything. Claude Desktop checks for changes at launch and about every 10 minutes while it runs, or every 30 minutes on older versions.
208208
209209### Connectors and plugins
210210
government/config/overview Changed · +1 / -1 lines
from line 6
66
77The Config page is where you set product behavior, such as session limits, which products members get, and telemetry, for the people you manage. To open it, go to **Settings > Config** in the admin portal. The same page appears at both the tenant and the organization level, with the same list of settings. For the settings themselves, see [Available settings](https://claude.com/docs/government/config/settings.md).
88
9<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-06-config-essentials.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=8624805f501e6ca7e01e12e6e94602ab" aria-label="Video walkthrough: Config essentials" />
9<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/QW2rDqtpaxS9YU5m/images/government/videos/admin-06-config-essentials-v2.mp4?fit=max&auto=format&n=QW2rDqtpaxS9YU5m&q=85&s=96c86f606126bba3b006c1950d4fa19d" aria-label="Video walkthrough: Config essentials" />
1010
1111Video: Config essentials (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
1212
government/config/plugins-and-connectors Changed · +1 / -1 lines
from line 8
88
99## Plugins versus connectors
1010
11A connector gives Claude access to another service, such as a search tool your agency runs. For adding a connector, see [Connectors](https://claude.com/docs/government/connectors/overview.md), and for what its tool policy means for members, see [Tool policy](https://claude.com/docs/government/connectors/overview.md#adding-a-connector).
11A connector gives Claude access to another service, such as a search tool your agency runs. For adding a connector, see [Connectors](https://claude.com/docs/government/connectors/overview.md), and for what its tool policy means for members, see [Tool policy](https://claude.com/docs/government/connectors/overview.md#tool-policy).
1212
1313A plugin is a package that changes how Claude works. It can add skills, slash commands, and sub-agents, and it can carry [hooks](https://code.claude.com/docs/en/hooks), which a plugin author sets to run automatically at defined points during a session, such as a command that runs when a session starts. Its hooks run on the member's machine. A plugin can also declare MCP servers of its own, and [Plugins that run code](#plugins-that-run-code) describes how they behave.
1414
government/org-admin/configuration Changed · +1 / -1 lines
from line 6
66
77In the organization view of the admin portal, go to **Settings > Config**. The Config page works the same way at the tenant and organization levels, with the same list of settings. See [How Config works](https://claude.com/docs/government/config/overview.md) for how levels, locks, and groups combine, and [Available settings](https://claude.com/docs/government/config/settings.md) for what each setting does.
88
9A setting marked **Locked by your tenant** can be changed only by a tenant administrator; see [Locks](https://claude.com/docs/government/config/overview.md#locks). Connectors and plugins the tenant has added are labeled **Inherited from your tenant** and cannot be changed from here. A connector or plugin you add with the same name takes priority over the inherited one for your members. See [Change or stop an inherited connector](https://claude.com/docs/government/connectors/overview.md#the-connectors-card) and [Where plugins are added](https://claude.com/docs/government/config/plugins-and-connectors.md#where-plugins-are-added).
9A setting marked **Locked by your tenant** can be changed only by a tenant administrator; see [Locks](https://claude.com/docs/government/config/overview.md#locks). Connectors and plugins the tenant has added are labeled **Inherited from your tenant** and cannot be changed from here. A connector or plugin you add with the same name takes priority over the inherited one for your members. See [Change or stop an inherited connector](https://claude.com/docs/government/connectors/overview.md#change-or-stop-an-inherited-connector) and [Where plugins are added](https://claude.com/docs/government/config/plugins-and-connectors.md#where-plugins-are-added).
1010
government/org-admin/overview Changed · +1 / -1 lines
from line 6
66
77The organization admin portal is where you manage the people, seats, and settings for a single organization in Claude for Government.
88
9<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-05-organization-owners-users-seat-tiers-and-readiness.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=d235ae566a0056c409a1b59b2a9623e7" aria-label="Video walkthrough: Organization owners: users, seat tiers, and Readiness" />
9<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/MtPmUtGcabx4sJAO/images/government/videos/admin-05-organization-owners-users-seat-tiers-and-readiness-v2.mp4?fit=max&auto=format&n=MtPmUtGcabx4sJAO&q=85&s=fbfcdaca92e3c17ff358af64f4f81ae5" aria-label="Video walkthrough: Organization owners: users, seat tiers, and Readiness" />
1010
1111Video: Organization owners: users, seat tiers, and Readiness (1 min 48 s). Narrated with an AI-generated voice, with on-screen captions.
1212
government/overview Changed · +2 / -2 lines
from line 36
3636
3737## The three views
3838
39<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" />
39<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/mGbOjjHMKV3LYuqi/images/government/videos/admin-01-finding-your-way-around-v2.mp4?fit=max&auto=format&n=mGbOjjHMKV3LYuqi&q=85&s=4aaba8c318c1a044b343874cc64c95c3" aria-label="Video walkthrough: Finding your way around" />
4040
41Video: Finding your way around (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
41Video: Finding your way around (2 min 24 s). Narrated with an AI-generated voice, with on-screen captions.
4242
4343[Transcript](https://claude.com/docs/government/video-walkthroughs.md#finding-your-way-around)
4444
government/tenant-admin/identity-and-access Changed · +2 / -2 lines
from line 85
8585
8686## SCIM provisioning
8787
88<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-04-directory-sync-scim-and-group-mappings.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=e254e02786c5f309b5c5c240c7752c4e" aria-label="Video walkthrough: Directory sync (SCIM) and group mappings" />
88<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gG0BlHWciPZj0Lhu/images/government/videos/admin-04-directory-sync-scim-and-group-mappings-v2.mp4?fit=max&auto=format&n=gG0BlHWciPZj0Lhu&q=85&s=44cfafd3709ce812b546449ea1dc0752" aria-label="Video walkthrough: Directory sync (SCIM) and group mappings" />
8989
9090Video: Directory sync (SCIM) and group mappings (2 min 3 s). Narrated with an AI-generated voice, with on-screen captions.
9191
from line 120
120120
121121## Routing rules
122122
123<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-03-organizations-seats-and-routing-rules.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=3b4fdf17a38f17ace0a31daff24dd678" aria-label="Video walkthrough: Organizations, seats, and routing rules" />
123<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gG0BlHWciPZj0Lhu/images/government/videos/admin-03-organizations-seats-and-routing-rules-v2.mp4?fit=max&auto=format&n=gG0BlHWciPZj0Lhu&q=85&s=c327b48633e8619e07ced55a9765ede5" aria-label="Video walkthrough: Organizations, seats, and routing rules" />
124124
125125Video: Organizations, seats, and routing rules (2 min 14 s). Narrated with an AI-generated voice, with on-screen captions.
126126