Kokeile ilmaiseksi
Kokeile ilmaiseksi
Alustan dokumentaatio

GitHub - Access & permissions

Viimeksi päivitetty {päivämäärä}

GitHub - Access & permissions

Elevale uses Personal access token (PAT) to read metrics from GitHub. Elevale does not modify data in the external system. Tokens and keys are encrypted server-side after validation.

Who can connect

  • Workspace admins and users with permission to manage Workspace Settings integrations.

  • Connections are managed from Workspace Settings → Integrations.

  • Requires [Business+] on your workspace plan.

What Elevale accesses

  • Read-only metrics exposed as KPI data points (see the Data points article).

  • Connection metadata (account IDs, property IDs, organisation tenants) needed for sync.

  • No write access to campaigns, repositories, accounting records, or CRM objects unless the provider API requires it for authentication only.

Elevale reads repository and organisation data using the permissions you grant on the token. It does not write to GitHub or modify repositories.

Required repository permissions (Read)

  • Metadata (automatic when any repo permission is added)

  • Contents repo details, releases, contributor stats

  • Issues issue counts and close-time metrics

  • Pull requests open, merged, and draft PR metrics

  • Deployments deployment and workflow metrics

Repository access scope

  • Only select repositories - recommended when KPIs target specific repos.

  • All repositories - for org-wide or multi-repo dashboards.

  • Public repositories only - not supported for KPI sync (GitHub hides repo permissions).

Organisation access (optional)

  • Add each GitHub org under Organization access on the token form.

  • Grant Members (Read) for organisation-level KPIs (org repo count, org open PRs, etc.).

Classic token alternative

  • Classic PAT scopes: repo, read:org, read:user. Fine-grained tokens are preferred for least privilege.

Disconnect and data retention