KeySkope
Start a free pilot
KeySkope / Documentation / GitHub
Documentation / GitHub

GitHub
Setup guide.

Review GitHub organisation membership and organisation owners without reading repository contents.

GitHub App · Reviewed 2026-09-26

Before you start

  • You must be an owner of the GitHub organization and an administrator in your KeySkope workspace.
  • Know your organization slug: the name after github.com/ in its address.
  • If your organization uses SAML SSO, sign in through its identity provider before authorizing.

You do not create a personal access token, upload a key, or create your own GitHub App.

Read-only permissions

The KeySkope GitHub App requests Organization → Members: Read-only. It reads organization members and identifies owners. Repository contents, secrets and write permissions are not requested.

Open the KeySkope GitHub App from this guide and confirm the app name and read-only permissions before approving. Select your company’s GitHub organization as the installation destination. If GitHub shows your personal account instead, return to the account selector and choose the organization.

Connect GitHub

  1. Open Connectors → GitHub in your KeySkope workspace.
  2. Choose Install the KeySkope GitHub App. On GitHub, select your company’s organization, review Members: read-only, and install. Choose the organization, not your personal account.
  3. Return to your KeySkope workspace. Enter the organization slug and choose Verify GitHub & connect.
  4. Authorize KeySkope using your GitHub organization-owner account. This confirms you can connect that organization to this workspace.
  5. You return to KeySkope and the first sync starts. Wait for it to complete, then review the results.

If you arrived here after installing the app, installation is complete. Return to your workspace and continue from step 3.

Connection details

Organization slug: for example, your-company. No token or secret is entered.

What appears in KeySkope

  • GitHub member IDs, usernames and Owner or Member access.
  • Owners are marked as privileged.
  • This preview does not collect repository-level access, outside collaborators, audit events or sign-in activity.
  • Member email addresses are not collected; accounts may remain unmatched to employees. Missing activity is unavailable, not proof of inactivity.

Verify the first sync

  1. Confirm the connector reports a successful, complete sync.
  2. Compare the members and owners with your GitHub organization’s People page.
  3. Check at least one owner and one ordinary member. Investigate partial or failed syncs before relying on the inventory.

Troubleshooting

  • Connection not completed: confirm the app is installed in the exact organization, authorize as an owner, and restart from KeySkope. The authorization link expires after ten minutes and can be used once.
  • SSO organization unavailable: establish your organization’s SAML session and authorize again.
  • Already connected elsewhere: ask KeySkope support to review the workspace binding.
  • Sync denied: check that the installation is active and retains Members: read-only.

Revoke or disconnect

In GitHub, open your organization’s Settings → GitHub Apps → KeySkope → Configure and uninstall the app to revoke its access. KeySkope checks installation validity on each sync. Reset the connector in KeySkope to stop its scheduled collection; previously collected history is retained. Reset alone does not uninstall the app from GitHub.

How authentication works

KeySkope protects its own app signing key and creates installation tokens that expire after one hour. Your personal authorization is used only to verify ownership during setup and is revoked after that check. Scheduled syncs use the organization installation.

Official references