Manage members and seats

Outcome

You can read your organization's seat usage at a glance, suspend and restore members, remove them entirely, and offboard someone without surprises — knowing exactly which of their assignments survive each action and how each action changes the seat count.

Who can do it

Only the organization's mapped owner or a site administrator can disable, enable, or remove members. The seat limit itself is a site-managed commercial setting: the site administrator sets a per-organization limit (or the deployment default applies). Owners cannot change their own limit.

Before you begin

• How seats are counted. Active members each consume one licensed seat. Disabled members free their seat. Every live pending invitation reserves one seat until it is accepted, revoked, or expires. The namespace owner does not occupy a seat.
• Offboarding consequences.
  • Disable suspends the member's access to the entire organization immediately — every granted repository disappears from their view — but keeps their repository access grants and named roles so Enable restores them exactly as they were.
  • Remove deletes the membership, all of their repository access, their named roles, and their organization capability grants. Re-adding them later means a fresh invitation and re-granting everything.
  • Neither action deletes the person's prpl account, and runs they launched themselves remain theirs.
• Re-enabling is seat-checked. Restoring a disabled member re-occupies a seat, so it fails when the organization is full — disabling cannot be used to smuggle extra members past the license.

Steps

1. Open your profile menu (top right), choose Settings, and find your organization's card in the Users section of the Account page.
2. Read the seat counter in the card header: seats used/limit, followed by a pending count when invitations are outstanding (for example seats 3/5 · 1 pending) and the member and repository counts.

3. Suspend a member: select Disable in their row. Their status changes to disabled, all access stops immediately, and their seat is freed. The page confirms Member updated.

4. Restore a member: select Enable in a disabled member's row. Their previous repository access and roles apply again unchanged. If the organization is full you will see the Seat limit reached message instead — free a seat first.
5. Remove a member: select Remove in their row. The membership, their repository access, and their roles are deleted, and the page confirms Member removed.
6. Free a reserved seat: under Pending invitations, select Revoke next to an invitation you no longer need. The reservation is released as soon as the page confirms Invitation revoked.
7. Need more seats? Ask your site administrator to raise the organization's seat limit — there is no self-service control for it.

Verification

• The seat counter reflects each change immediately: disabling drops the used count, enabling raises it, revoking an invitation lowers the pending count.
• A disabled member's status reads disabled, and signed in as them, the organization's repositories no longer appear (their Account page shows access suspended for the organization).
• A removed member no longer appears in the member table, and they no longer appear in any repository's Per-repo access rows.

Troubleshooting

• "Seat limit reached — all licensed seats for this organization are in use. Remove or disable a member to free a seat." You tried to re-enable a member (or invite one) while full. Disable or remove someone, revoke a pending invitation, or request a higher limit from your site administrator.
• The invite form is gone. When used seats plus pending invitations reach the limit, the form is replaced by All N licensed seat(s) are in use — remove or disable a member to invite another user. This is the same seat-full condition, counted with reservations.
• You removed someone by mistake. Removal cannot be undone in place. Send a fresh invitation (Invite members with initial repository access) and re-grant their repositories and roles (Assign repository access and roles). Prefer Disable when there is any chance the person returns.
• A disabled member still shows in the member table. That is intended — disabled members stay listed (greyed, status disabled) so you can re-enable them. Only Remove deletes the row.

Next step

With the roster settled, keep the estate healthy from the dashboard: Use the organization risk dashboard.