---
title: How do you track GitHub Copilot usage when your company has several GitHub enterprise accounts?
url: https://opencontroller.lyzr.com/blog/track-github-copilot-usage-across-multiple-enterprises
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# How do you track GitHub Copilot usage when your company has several GitHub enterprise accounts?

**GitHub reports Copilot usage per enterprise and per organisation, so connecting one enterprise shows only that enterprise. To see everything, list every enterprise and standalone organisation you pay for, enable the "Copilot usage metrics" policy in each, grant a read-only token or GitHub App per enterprise, and merge the reports on a resolved employee identity. Expect the largest gap to be a separate R&D or acquired-company enterprise.**

Large companies rarely have one GitHub account. Mergers, separate R&D groups, regional subsidiaries and early pilots each create their own enterprise or organisation. A dashboard that looks complete can be missing most of the usage.

## Why does one connected enterprise miss Copilot usage?

Because every Copilot metrics endpoint is scoped to a single account.

| Scope | Endpoint family | Who can read it |
|---|---|---|
| Enterprise | `/enterprises/{enterprise}/copilot/metrics/reports/` | Enterprise owners, billing managers, or users with the "View Enterprise Copilot Metrics" permission |
| Organisation | `/orgs/{org}/copilot/metrics/reports/` | Organisation owners, or users with "View Organization Copilot Metrics" |

Each scope offers 1-day and 28-day reports for the account, its users, repositories and user-team joins. Nothing aggregates across enterprises. A token issued in enterprise A returns nothing about enterprise B.

Two more details catch teams out:

- The enterprise endpoints only work when the **"Copilot usage metrics" policy is set to "Enabled everywhere"** for that enterprise.
- Daily enterprise and user reports go back up to one year, with data available from 10 October 2025. If you connect late, backfill quickly.

## How do you find every enterprise and organisation?

Do not rely on what the platform team knows about. Use money and identity as the source of truth.

1. **Ask procurement for every GitHub invoice and marketplace charge.** Each billing account maps to an enterprise or a standalone organisation.
2. **Search corporate card and expense data** for GitHub and Copilot charges. Small teams often buy Copilot Business on a card.
3. **Check your identity provider** for every GitHub SAML or OIDC application. Each usually points to a separate enterprise.
4. **Look for Enterprise Managed Users accounts.** Usernames in a managed enterprise carry an underscore and a short code suffix, which identifies the enterprise they belong to.
5. **Ask acquired companies directly.** Their enterprise may still be billed to the old entity.

Record each account with an owner, billing contact and Copilot plan in your AI inventory.

## How do you connect each enterprise?

For every enterprise and standalone organisation:

1. Set the Copilot usage metrics policy to "Enabled everywhere".
2. Create a GitHub App or fine-grained token with read access to Copilot metrics only. Fine-grained tokens need the "Enterprise Copilot metrics" (read) permission at enterprise level, or "Organization Copilot metrics" (read) at organisation level. Avoid classic personal tokens tied to one administrator.
3. Pull `users-1-day` daily and `enterprise-28-day/latest` weekly.
4. Store reports with the enterprise slug as a column so you can always tell the source apart.

## How do you reconcile users across enterprises?

The same person can appear in several enterprises under different usernames. That causes two problems: double-counted usage and paying for two seats.

| Problem | Symptom | Fix |
|---|---|---|
| Different usernames per enterprise | One employee appears as two or three users | Resolve each login to a corporate identity through the identity provider or SAML identity, not by string matching |
| Seats in more than one enterprise | Seat count exceeds headcount of developers | Each enterprise bills its own seats; remove the duplicate seat in the enterprise the person uses least |
| Missing email on profiles | Usage cannot be joined to HR data | Use SAML or SCIM identity links rather than public profile email |
| Departed employees | Seats still assigned months later | Tie seat removal to the leaver process in every enterprise |

Report a single figure per employee and per cost centre, with the enterprise as a drill-down.

## How Opencontroller helps

Opencontroller Edge extends control to developer devices and coding agents and is installed by IT through MDM. Opencontroller's governed registry records agents, tools and MCP servers in one place, and its policy as code applies across the estate. See the cross-platform pillar, [how to govern AI agents across platforms](/blog/how-to-govern-ai-agents-across-platforms), and the [AI agent control plane explainer](/blog/what-is-an-ai-agent-control-plane). [Book a demo](https://www.lyzr.ai/book-demo/) to see it on your estate.

Related: [attribute GitHub Copilot usage to employees](/blog/attribute-github-copilot-usage-to-employees) and [find unused AI seat licences](/blog/find-unused-ai-seat-licences).

## Frequently asked questions

**Can one token read Copilot metrics for several enterprises?**
Not in practice. Endpoints are scoped per enterprise or organisation, and permissions are granted per account, so plan one credential per enterprise.

**Why do the enterprise metrics endpoints return an error?**
The most common cause is the "Copilot usage metrics" policy not being set to "Enabled everywhere" for that enterprise.

**How far back can we pull Copilot usage?**
Daily enterprise and user reports reach back up to one year, with data starting from 10 October 2025.

## Key facts

GitHub Copilot usage metrics are scoped per enterprise (/enterprises/{enterprise}/copilot/metrics/reports/) or per organisation (/orgs/{org}/copilot/metrics/reports/); nothing aggregates across enterprises. Enterprise endpoints require the "Copilot usage metrics" policy set to "Enabled everywhere". Daily enterprise and user reports go back up to one year, with data from 10 October 2025. Fine-grained tokens need "Enterprise Copilot metrics" or "Organization Copilot metrics" read permission. Enterprise Managed Users usernames carry an underscore and short code suffix. Opencontroller Edge extends control to developer devices and coding agents via MDM. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How do you attribute GitHub Copilot usage and cost to employees across several GitHub enterprises?](https://opencontroller.lyzr.com/blog/attribute-github-copilot-usage-to-employees.md)
- [How do you find unused GitHub Copilot, ChatGPT Enterprise and Claude seats?](https://opencontroller.lyzr.com/blog/find-unused-ai-seat-licences.md)
- [How do you link AI usage records to employees when every tool uses a different identifier?](https://opencontroller.lyzr.com/blog/identity-resolution-for-ai-usage-data.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
