Skip to main content
Telara

Integrations / GitHub Copilot

GitHub Copilot logo

GitHub Copilot

GitHub Copilot — usage metrics + seat assignment for AI platform spend governance. Distinct from the GitHub SCM connector; this governs Copilot spend and developer-productivity signals only.

OAuth 2.0
Spend
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A GitHub organization (or enterprise) with Copilot Business or Enterprise.
Org owner, billing manager, or a custom role that can view Copilot metrics. This is not the GitHub source connector.

Vendor setup

Get the credential

1
Create a token (or use the GitHub App)
Create a GitHub personal access token, or use a GitHub App installation token, for the org Telara should report on. Grant the permissions this page lists from the catalog — do not copy a permission list from an old wiki.
2
Paste in Telara
Settings → Integrations → GitHub Copilot. Paste the token. Name the organization if the form asks.

Permissions Telara requests

  • manage_billing:copilot
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

GitHub OAuth App authorization-code connection for Copilot billing administration. This requests manage_billing:copilot; retain the API-key/PAT or GitHub App route when a customer only authorizes read-only organization access.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

API key

GitHub personal access token (classic) or fine-grained PAT, OR a GitHub App installation token. Required scopes depend on which report scope you target: - Organization-level reports (/orgs/{org}/copilot/...): read:org - Enterprise-level reports (/enterprises/{enterprise}/copilot/...): manage_billing:copilot OR read:enterprise - List Copilot seats (/orgs/{org}/copilot/billing/seats): manage_billing:copilot OR read:org - Copilot cloud agent permissions (/orgs/{org}/copilot/coding-agent/...): admin:org A GitHub App alternative needs Copilot Business "Read" permission on the target org or enterprise. The caller must additionally be enterprise admin, org owner, billing manager, or hold an enterprise custom role with "View Enterprise Copilot Metrics".

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by directory ID.

Vendor history: 365 days of vendor-side history.

  • suggestions_shown
    count
  • suggestions_accepted
    count
  • lines_suggested_added
    count
  • lines_suggested_deleted
    count
  • lines_accepted_added
    count
  • lines_accepted_deleted
    count
  • chat_total_messages
    count
  • chat_total_acceptances
    count
  • chat_agent_mode_interactions
    count
  • chat_ask_mode_interactions
    count
  • chat_edit_mode_interactions
    count
  • active_users
    count
  • assigned_seats
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A token that can clone code is not enough. Copilot usage reports need the billing/metrics permissions this page lists.
Personal Copilot on a free or Pro seat has no org usage API. That is a plan mismatch, not a Telara outage.