GitHub
The GitHub connector supports Identity & Access records and Assets & Data resources for one GitHub organization.
Required values
- Personal Access Token for the connector
- Organization Name for the GitHub organization Superviso should read
Required access
Grant read access to organization members and repository metadata:
- Organization permissions: read access to members
- Repository permissions: read access to metadata
Prefer a fine-grained token restricted to the intended organization and only the repositories that should be visible to Superviso.
Before you start
Create the credentials listed above in the provider’s administration tools.
Configure in Superviso
- Open Settings → Connectors and choose Add connector.
- Select GitHub from Provider.
- Associate the intended asset, or use the new-asset option when appropriate. Enable only the supported synchronization options you need.
- Enter Personal Access Token and Organization Name for the intended organization.
- Recheck the required privileges, scope, and filters, then choose Create connector. Resolve any validation errors shown by the form.
- Open the saved connector, choose Sync connector when available, and confirm the synchronization scope.
- Open Logs, wait for execution to finish, and inspect the result and any errors. Open the relevant Identities, Privileges, or Resources page for the enabled integration to verify collected records.
Expected outcome
The connector is saved for GitHub with the intended integration and collection scope. Synchronization logs show progress, results, and imported records.
If setup or synchronization fails
Check the exact account or organization identifier, required form values, credential validity, granted access, and selected filters. Inspect the failed log’s details before retrying. If only some records are missing, check their scope and provider permissions. For synchronization status and source-managed fields, see Connectors and synchronization logs.