GitHub Copilot

Pull Copilot usage and invoiced cost from GitHub so you know who's actually using it — and whether the spend is paying off. Since June 2026 Copilot bills on usage (AI credits), so the question isn't just "who has a seat" but "who is burning the credits".

What syncs

Data	Description
Invoiced cost	Copilot spend in USD per day, straight from GitHub's billing platform
Per-user activity	One row per user per day: interactions, code generated and accepted, lines of code, which surfaces they used (chat, agent, CLI)
AI credits	Each user's daily AI-credit consumption (GitHub's usage-billing unit)

Per-user data comes from GitHub's Copilot usage-metrics reports. GitHub publishes these within two full days of each day closing, so the most recent day or two is always empty — that is expected, not a fault. Reports begin on 10 October 2025 and reach back one year from today, which bounds how much per-user history a first connect can recover.

Invoiced cost reaches further back than the per-user reports, though GitHub does not state a retention figure for the organisation billing endpoint, so Flowstate makes no promise about exactly how far.

What you'll see in Flowstate

• Spend reconciliation — Copilot's invoiced cost next to actual per-user activity. See /ai-governance/insights/spend.
• Per-person usage — who is actively using Copilot, keyed by GitHub login; link logins to employees in the data-mapping screen and everything attributes to real people.
• Per-project attribution — combined with the Flowstate Agent, Copilot usage is attributed to projects. See Attribution.
• Adoption and trends — track who's genuinely active and how the curve is moving.

Getting started

Before you start, two GitHub-side prerequisites:

• Your organisation must be on GitHub's enhanced billing platform (all usage-billed orgs are).
• The enterprise policy "Copilot usage metrics" must be set to Enabled everywhere, or GitHub will not generate the per-user reports.

Then:

1. Create a GitHub token that can read your organisation's billing and Copilot metrics (classic PAT with read:org, or a fine-grained token with the View Organization Copilot Metrics permission plus billing read)
2. Go to Settings → Integrations and open the GitHub Copilot tile
3. Enter your GitHub organisation name, paste the token and click Verify and connect — Flowstate makes one read-only call to check it works before saving anything

Usage syncs hourly; the first connect backfills cost history and per-user reports (the latter reaching back at most one year, and no earlier than 10 October 2025). If the per-user reports are unavailable — usually the enterprise policy above — cost still syncs, and the connection's provider page shows exactly what GitHub returned.