Skip to content
PromptGlassDocs

GitHub Copilot

The GitHub Copilot connector reads the GitHub REST API for Copilot seats and metrics at the organization and enterprise level. You get seat utilization (who has a seat, when they last used it), engagement metrics such as suggestions, acceptances, chat turns and active users by editor and language, and team-level rollups joined to your identity provider.

Permissions

Section titled “Permissions”

Create a GitHub App (recommended) or a fine-grained token with:

  • Organization permissions → GitHub Copilot Business: Read
  • Organization permissions → Members: Read
  • For enterprises: an enterprise-owner token with manage_billing:copilot (read)
Terminal window
promptglass connectors add github-copilot \
  --org acme --app-id 123456 --private-key-file ./pg-copilot.pem

Data collected

Section titled “Data collected”
Endpoint Data
GET /orgs/{org}/copilot/billing/seats Seat holders, last_activity_at, last_activity_editor
GET /orgs/{org}/copilot/metrics Daily active/engaged users, completions, acceptances, chat, by editor and language
GET /orgs/{org}/team/{team}/copilot/metrics The same, per GitHub team

What PromptGlass adds

Section titled “What PromptGlass adds”
  • Idle seats: seat holders with no activity in a configurable window, with projected savings. See cost optimization.
  • Identity join: maps GitHub logins to directory users (via SAML/SCIM external identities), so Copilot appears in the same department view as ChatGPT and Claude.
  • Overlap: developers who hold both a Copilot seat and a Cursor or Claude subscription.
  • Code leakage: Copilot’s API doesn’t expose prompt content. For DLP on code sent to AI assistants, route IDE traffic through the forward proxy.