How can I display results for multiple Organizations within a single EMU Enterprise instance?

[dehrenheim]

I have our instance configured to display the results by Organization, but we have multiple Orgs. How can I set it up to display for multiple Orgs?

I also have a billing API token set to retrieve the billing information and I have a GitHub App setup to authenticate users. As a Billing Admin I can see all of my usage under the Billing Tab, but when I look at it under the My Usage tab I only see some of my usage and not all. If I try and set it up to display the Enterprise, I get a 403 error and permission denied, but can X out of the message and still retrieve some of the information. I think the issue for my user is because I Admin the instance and I am a member of several of the Orgs. We will be moving to granting the majority of licenses at the Enterprise level and use some of the Orgs for testing new models/features. Is there any way that I can make this work for our situation so that I am able to see the same information from both the Billing Tab and the My Usage tab?

Here is the error message:
403 Forbidden from GitHub: Error fetching seats data. Error: FetchError: [GET] "https://api.github.com/enterprises/company-name/copilot/billing/seats?per_page=100&page=1": 403 Forbidden. Common causes: (1) classic PAT missing 'read:org' scope (required for seats and per-user metrics), (2) fine-grained PAT not supported for this endpoint, (3) account lacks org owner / billing manager / Copilot admin role, or (4) PAT not SSO-authorized for this org.

Thanks,
Daryl

[identity-wael]

The 403 you've pasted is specifically from the enterprise seats endpoint. Its permissions differ from both organization metrics and AI-credit billing, so the working Billing tab doesn't prove that the seats request has the right credential.

For GET /enterprises/{enterprise}/copilot/billing/seats, GitHub currently requires an enterprise owner or billing manager using a classic PAT with read:enterprise or manage_billing:copilot. GitHub App tokens and fine-grained PATs are not supported by that endpoint. The generic read:org suggestion in the error is therefore misleading for this URL.

For an enterprise-wide dashboard, the relevant public configuration is:

NUXT_PUBLIC_SCOPE=enterprise
NUXT_PUBLIC_GITHUB_ENT=your-enterprise-slug

Then verify which credential the server actually sends for seats. In the current authentication code, configured backend GitHub App credentials take precedence over NUXT_GITHUB_TOKEN. This is separate from using an app to sign users in. The seats handler uses those request headers; it does not automatically use NUXT_GITHUB_BILLING_TOKEN merely because the URL contains /billing/seats.

I would first make a read-only request to that exact endpoint with the intended backend credential, then ensure the dashboard is using the same credential and enterprise slug. Keep the dedicated billing token/enterprise setting for AI-credit billing as documented in the README.

Enterprise scope is the appropriate aggregate when access is granted across multiple organizations/enterprise teams; don't put a comma-separated list into the single organization slug. Also, Billing spend and My Usage activity are different datasets, so fixing this 403 should restore seats access but doesn't by itself guarantee identical totals across those views. Compare the same user, date range, and metric after the authorization issue is resolved.