# Seat Allocation

One paid seat of a subscription assigned to an account. A seat is an entitlement, never a permission.

A Seat Allocation consumes one seat of a Subscription. Permissions live only in Access Grant. The table had no rows on 2026-10-28.

## Rules and relationships

Link one Subscription and, once it exists, the Account that occupies the seat; leave Account blank while the seat is Requested. Move Tool Access Status through Requested → Verified, or Failed, and finally Revoked. A revoked seat may leave a grant to clean up.

The Shared description asks you to link the unit in Shared With and the leader in Responsible, but neither field exists in the base. Until they do, describe the unit in a Tag or leave the seat unshared.

## Fields

| Field | Storage | Current configuration |
| --- | --- | --- |
| Seat # | Auto number | Running number of the seat |
| Domain Role | Text | The tool's role word for the seat; not a permission |
| Shared | Checkbox | Ticked = used by a unit, not one holder |
| Tool Access Status | Single select | Requested, Verified, Failed, Revoked |
| Subscription | Linked records | [Subscription](/systems/tooling/entity-subscription); Multiple-record picker |
| Account | Linked records | [Tool Account](/systems/tooling/entity-tool-account); Multiple-record picker |
| Tags | Linked records | [Tags (mirror)](/systems/tooling/entity-tags); Multiple-record picker |

## Example

Subscription = Business+; Account = ana.costa; Domain Role = Editor; Tool Access Status = Verified.

## Next steps

[Record plans, seats and grants](/systems/tooling/record-access) · [Find the view](/systems/tooling/data-views)