GitHub Copilot seats

Access

Kind

Sign in on the vendor's page; nothing typed here

What to give

Fine-grained token, Copilot read

Why that one

A fine-grained personal access token whose resource owner is your organization, with two organization permissions set to read-only, GitHub Copilot Business and Organization Copilot metrics, 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; suggestions shown and accepted, lines, agent and chat use, editor and language per person-day; pull requests Copilot opened, per day

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/
• https://api.github.com/app/installations/
• https://copilot-reports.github.com/

Valistry calls only these addresses. It blocks any other call and logs every call.

Connecting it

1. Enable usage metrics. In your organization: Settings → Copilot → Policies. Set Copilot usage metrics to Enabled. Open ↗
2. Create a fine-grained token. Click Open GitHub. Check the values below, then click Generate token. Open ↗

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.

Settings worth turning on in GitHub

1. Give seats through teams. Each seat then carries the team that gave it. Valistry reads it.
2. Turn on usage metrics. The usage dashboards need the Copilot usage metrics policy on.
3. Create cost centers. Group users so AI credit spend splits by group.
4. Set AI credit budgets. Limit AI credits per user, cost center or enterprise.

Questions about GitHub Copilot