GitHub’s changelog, dated 10 November 2026, says enterprise GitHub Apps can now call the enterprise-level Copilot seat management APIs. They can control which users and enterprise teams hold Copilot seats, using a new fine-grained permission called “Enterprise Copilot license management”.
What changed
Until now, seat decisions typically meant an administrator clicking through settings. A GitHub App is automated software, so seat allocation can now be tied to something else: an HR system, a project start date, or a contractor’s contract end. The changelog links to API documentation (version 2026-03-10) but does not list endpoints, rate limits or extra eligibility rules, so check those before building anything on it.
Why buyers should care
AI coding tools have shifted from a developer’s personal choice to a managed line item. Seats cost money, and unused ones are waste. We have covered the billing and budget changes in earlier signals; this is the control layer that sits behind them. The question for a commissioning team is no longer “do our developers use Copilot” but “who approved each seat, and does it end when the engagement does”.
What it means for suppliers
If an agency or contractor works in your repositories, ask how their AI tooling access is granted and revoked. Automated seat management makes a clean answer possible. A vague answer is worth noting.
So what
When you commission software, put AI tooling access in the same conversation as repository access: who holds it, on whose licence, and when it ends. Our AI-assisted development service sets these terms out at the start. If you want that written into a delivery plan, start a project.