Skip to main content
Regentra can store a GitHub personal access token for your organization and verify it’s valid. This is a credential-connection integration today — Regentra does not yet automatically pull repository metadata, branch protection rules, pull-request reviews, or org member data from GitHub.
Automated evidence collection from GitHub (repositories, branch protection, PR reviews, org members) is not implemented yet. Connecting today saves and validates your token for when that ships.

​
Setup

1

Generate a fine-grained Personal Access Token

Open github.com/settings/tokens and select Fine-grained tokens. Click Generate new token.
2

Set the resource owner

Set the resource owner to your organization. If you don’t see your org, an org admin needs to enable fine-grained tokens for the org first.
3

Choose repository access

Under Repository access, choose either All repositories or specific repositories.
4

Grant read-only permissions

Grant read-only permissions for:
  • Repository → Metadata (read)
  • Repository → Contents (read)
  • Repository → Pull requests (read)
  • Organization → Members (read)
5

Enter token in Regentra

In Regentra, go to Settings → Integrations and find the GitHub card. Paste the token into Personal Access Token, and your org’s URL slug (e.g. my-org from github.com/my-org) into Organization Name.
6

Save and test

Click Save Credentials, then Test Connection. A successful test confirms the token is valid and shows the GitHub account name and how many organizations it belongs to.
Test Connection checks the token itself (via GitHub’s /user and /user/orgs endpoints) — it doesn’t currently verify the token against the specific organization name you entered.

​
Frequently asked questions

Fine-grained tokens are scoped to a specific org and a specific permission set, and they expire by default. Classic PATs grant broad access tied to a user account. Fine-grained is the lower-blast-radius choice.
An org admin needs to enable them under Settings → Personal access tokens. Until that’s done, classic PATs work but with broader scope — request the read:org and repo (read-only via SAML) scopes if you must.
Fine-grained tokens expire on a date you set during creation (default 30 days). Pick something reasonable and rotate before it lapses — a request made with an expired token fails Test Connection with a GitHub authentication error.