Seats changedgovernment/tenant-admin/seats
Nearest release: v2.1.234, published under an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−2removed
From line
37
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 37, old and new numbered
/
from line 37
3737
3838## How seats affect new users
3939
40When a new person is placed in an organization (by a routing rule on the [Identity and access](/docs/government/tenant-admin/identity-and-access) page), they're automatically given a seat if one is free. Tiers are filled in a fixed order, so the first tier is filled before the next is started. If every tier the organization has is completely full, the new person is placed in the organization without a seat. They can sign in and see the portal, but cannot send messages to Claude until an owner assigns them a seat or you distribute more seats here.
40When a new person is placed in an organization (by a routing rule on the [Identity and access](/docs/government/tenant-admin/identity-and-access) page), they're automatically given a seat if one is free. Tiers are filled in a fixed order, so the first tier is filled before the next is started. If every tier the organization has is completely full, or the organization has no seats distributed to it yet, the new person is placed in the organization without a seat. They can sign in and see the portal, but cannot send messages to Claude until someone gives them a seat tier. An organization owner can do that on the organization's Users page, and so can you from the organization's admin view.
4141
42An organization that has no seat allocation at all is treated as uncapped. New users can join and use Claude, but this is unusual; normally every active organization has at least one tier allocated.
42The first seats you give an organization are also used for the people already in it. If nobody in the organization holds a seat when you save its first allocation, members without a seat tier are seated automatically from those seats, Primary Owners first. This covers an organization that was created with only a Primary Owner and given seats afterwards. Anyone the new seats do not cover stays without a seat tier until an owner assigns one. Later changes to an allocation do not repeat this. They add or remove free seats for new arrivals and for the organization's owners to assign, and directory-provisioned users with a group-to-tier mapping are seated from the added seats on the next sync.
4343
4444## When you can't edit
4545
No line in this hunk matches that.