Skip to main content

Configuring GitHub Copilot (Fine-Grained PAT)

Track GitHub Copilot adoption and usage using a fine-grained Personal Access Token (PAT) with scoped organization access and more granular permission control.

Steven Silverstone
Updated by Steven Silverstone

Overview

LinearB integrates with GitHub Copilot using a fine-grained Personal Access Token (PAT) to track AI adoption and usage with scoped organization access.

This integration provides more granular permission control compared to classic PATs and is suitable for organizations that require tighter security policies.

Note: This integration may not yet be available in all environments.

Before You Begin

  • LinearB role: Company Admin
  • GitHub permissions: Organization owner/admin
  • Copilot Usage Metrics policy enabled in GitHub
  • The GitHub user who creates the token must also have an organization role with the view organization Copilot metrics permission
Important: Both the PAT permission and the GitHub organization role are required. Configuring only one of them is insufficient.

Step 1 — Enable Copilot Usage Metrics in GitHub

Ensure that Copilot usage metrics are enabled in your GitHub organization settings.

  • Required to retrieve Copilot usage data
  • Missing permissions may result in 403 Unauthorized errors

Step 2 — Create a Fine-Grained Personal Access Token

  1. Create a fine-grained Personal Access Token in GitHub.
  2. Set the resource owner to the GitHub organization whose Copilot data you want to track.
  3. Scope the token to the relevant organization.
  4. Under Permissions, grant access to:
    • GitHub Copilot metrics (read)
  5. Read-only access is sufficient. No write permissions are required.
  6. Copy and securely store the token.
Fine-grained tokens provide more precise access control compared to classic PATs.

Step 3 — Grant the Token Owner the Required Organization Role

The token owner must also have an organization role that includes the view organization Copilot metrics permission.

Without this role, GitHub Copilot metrics cannot be collected even if the token includes the required API permission.

Create the role

  1. In GitHub, go to Organization → Settings → Organization roles.
  2. Click Create role.
  3. Name the role (for example, Copilot View).
  4. Select the view organization Copilot metrics permission.
  5. Save the role.

Assign the role

  1. Go to Organization roles → Role assignments.
  2. Assign the role to the GitHub user who created the fine-grained PAT.
Tip: If the integration fails after the token is generated, verify that the token owner has been assigned the required organization role before generating a new token.

Step 4 — Connect Copilot in LinearB

  1. Go to Settings → Company Settings → AI Tools → GitHub Copilot.
  2. Paste the token.
  3. Select the organization scope.
  4. Click Save.

Once connected, Copilot data will begin syncing and appear in AI dashboards.

Historical Data & Backfill

  • Up to 90 days of data may be backfilled
  • Data updates on a daily cadence

Where Copilot Data Appears

  • AI Tools Usage
  • AI Adoption
  • AI Insights Dashboard
  • AI Analytics Dashboard

Troubleshooting

GitHub Copilot Troubleshooting

How did we do?

Configuring Cursor

Configuring GitHub Copilot (PAT Classic)

Contact