GitHub Copilot seats
The Copilot seat list and plan: who holds a seat (stored as a hash, never the login), since when, the assigning team, and whether GitHub saw activity in the last 28 days. Never code, never repositories, never members.
Access
- Kind
- A read-only key you paste
- What to give
- Fine-grained token, Copilot read
- Why that one
- A fine-grained personal access token whose resource owner is your organization, with the organization permission GitHub Copilot Business set to read-only and nothing else. Only an organization owner can create it: GitHub restricts seat information to owners. Tested first, then stored encrypted; shown only as its last four characters.
What it attributes on its own
- From the source
- seat holder (hashed) · assigning team · plan · activity in the last 28 days
- Needs a rule or a trace
- tokens and models — GitHub does not expose them per seat · the charge itself — seats × list price stands in · outcome — needs the pull-request join
The addresses it calls
- https://api.github.com/orgs/
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Sign in as an organization owner. GitHub shows Copilot seat information to organization owners only; a token made by anyone else is refused.
- Create a fine-grained token. Click Generate new token and fill the form: Open ↗
- Copy the token and paste it below with the organization. It is shown once. Test and connect reads the plan and the seat list, reports what worked, and stores the token only if the read succeeded.
A classic token with the read:org scope also works, but read:org exposes teams and membership across every organization you belong to. The fine-grained token above reads Copilot seats only.