GitHub Apps can manage Copilot seats, with billing and permission limits

GitHub Apps can now manage enterprise Copilot seats through the enterprise-level APIs. GitHub’s November 10 update adds the fine-grained Enterprise Copilot license management permission for this work. It gives administrators an app-based automation route, not free seats or a new coding model.

The API reference still labels these endpoints public preview and subject to change. The useful distinction is between reporting on assigned seats and granting an app authority to purchase or cancel them.

Read access and write access do different jobs

GitHub documents App user tokens and installation tokens for the enterprise endpoints. Listing seats accepts read access to Enterprise Copilot license management. Adding or removing assignments requires write access. Enterprise administration is an alternative permission, but a seat-only integration should not request broader authority merely for convenience.

The list response also needs interpretation. Its total counts a person once, while the seat-detail array can contain several assignment records for that person. IDE activity depends on telemetry being enabled. An absent activity timestamp is therefore not enough evidence to conclude that someone no longer needs Copilot.

A sensible first deployment is a report-only reconciliation: compare the intended roster with existing assignments and have a licensing owner inspect the proposed differences. Keep the report and mutation paths separate, so a reporting error cannot silently become a purchase.

Enterprise installation is a separate approval boundary

The enterprise App installation guide says enterprise owners can install these Apps. App managers cannot. An enterprise installation grants the requested enterprise permissions, not general access to the enterprise’s organizations or repositories. Those resources need separate installations where applicable.

GitHub also documents no webhook support for enterprise installations at present. Do not design the reconciliation process around an assumed enterprise event stream. When acting through a user token, the user must themselves be allowed to perform the operation.

Before approval, identify the app owner, the exact permission level and the enterprise it will affect. Set a maximum change batch and a human review point for unexpected roster differences. These are deployment recommendations, not safeguards GitHub claims to add automatically.

Adding seats can create a bill

The API describes an add operation as purchasing seats. Removing an enterprise-team assignment sets seats to pending cancellation, with access normally ending at the billing-cycle boundary unless another team retains it. A successful removal response is not a promise of an immediate refund.

GitHub’s billing guide lists Copilot Business at $19 USD per user monthly and Copilot Enterprise at $39, including 1,900 and 3,900 pooled AI credits respectively. Additional usage is billed separately. Mid-cycle additions are prorated, and removed seats remain billed through the current cycle. Credit-card and PayPal customers can face an upfront prorated charge when seats are added.

For illustration, ten additional Business seats represent $190 at a full month’s list rate before metered overage. That is arithmetic, not a quote for a particular account. A preview of the affected people and expected billing impact is more useful than a bare confirmation that an API request succeeded.

Do not confuse this with the new Copilot access plan

GitHub’s separate billing transition guide describes eligible enterprises receiving Copilot access without an incremental seat charge for GitHub Enterprise Cloud license holders, or $10 monthly for standalone users. That model includes no usage allowance. Transition is voluntary, and the page currently says self-serve subscriptions are not eligible.

The App-permission announcement does not establish that every billing model supports every preview endpoint. Confirm the account’s plan and the endpoint’s documented prerequisites before enabling writes. ByteForward has not installed an App or executed seat-management requests for this coverage.

AI-generated editorial illustration by ByteForward. Access cards are conceptual, not a GitHub interface. GitHub branding identifies the subject of independent reporting. ByteForward is not affiliated with or endorsed by GitHub.