Summary

  • In GitHub's public-preview installation-token path, an App installed on an organization can request Copilot without a user signing in if it has the organization Copilot Requests permission set to Read-only. The organization pays in AI credits, under its model and spending controls. GitHub does not offer an individual App or installation budget.
  • App attribution appears in an AI usage CSV through app_client_id, not the on-screen AI usage view. To stop one App installation, an owner can suspend or uninstall it, also cutting that installation's access to other organization resources.

The permission name is a lousy purchase order

An organization owner reviewing a GitHub App sees a permission called Copilot Requests: Read-only. That label sounds like an observer's pass. GitHub's own guidance says the permission lets an organization-installed App make Copilot requests with an installation access token, without any user signing in. The requests consume the organization's AI credits. Read-only is about the permission type; it is no promise that the meter stays still.

The boundary is specific. This public-preview route covers Apps installed on an organization, not installations on personal accounts or enterprises. The App needs that organization permission. It can use only models permitted by the organization's Copilot policies, and the organization's billing and spending controls apply. GitHub explicitly separates this path from a user's authorization, from the policy that allows Copilot CLI use billed to the organization, and from Actions workflows using GITHUB_TOKEN. Lumping those identities together makes the resulting spend harder to explain.

The organization pays, but cannot draw a spending fence around one App. GitHub says it cannot create a budget for an individual App or installation. Usage from an organization-installed App counts toward the organization's Copilot budget. An alert-only budget sends a message after the threshold; it does not stop further requests. A hard stop needs Stop usage when budget limit is reached. That is an organization-wide control over consumption, not a personal allowance for the App that requested the tokens.

To find the App, leave the dashboard

The AI usage view on GitHub does not display App attribution. GitHub directs owners to export the AI usage report as CSV and look for rows with the organization in the organization column and a populated app_client_id. GitHub's published instructions tell owners to match that value to client_id in the organization's App installation API response and use app_slug to identify the App. This is a legitimate audit trail, but it is not the quick glance an owner might expect from a spending dashboard.

An empty app_client_id needs careful reading. GitHub says user-attributed use, Actions, other GitHub-owned Apps and historical usage from before App attribution was available can all leave it blank. A blank cell does not prove that no automation consumed credits. Nor does a populated cell itself prove abuse. It identifies the installation path whose usage belongs to the organization.

GitHub's billing guide prices one AI credit at US$0.01. It describes Copilot Chat, CLI, cloud agent, Spaces, Spark and third-party coding agents as consumers of AI credits, while inline code completion and next edit suggestions remain outside that meter. Plans differ in whether they provide a shared monthly pool or bill from the first metered use. The public documents establish the unit and payer, not the volume of any named App's traffic. The amount charged to any named App requires that organization's usage and billing records.

The off switch is wider than the spend

An owner can suspend or uninstall one App installation to stop its Copilot requests. GitHub warns that this also blocks that installation's access to other organization resources. The targeted budget that could have stopped only its AI-credit use does not exist in the documented controls. Owners instead choose among model policy, organization spending limit and a suspension that may interrupt unrelated App functions.

The decision belongs at installation approval. Ask what the App will request, which models it may use, how usage will be attributed in CSV, and who can suspend it if the organization budget starts moving. The permission is Read-only. The economic decision is not.

Sources