Skip to main content
ConfigView pulls GitHub data through one Personal Access Token (PAT) with enterprise-level scopes, plus your enterprise slug. The same PAT covers all 46 endpoints — there is no separate SCIM, billing, or audit credential. You will end up with 2 secrets in ConfigView (GITHUB_TOKEN, GITHUB_ENTERPRISE_SLUG) when setup is complete.
Plan requirement. Most endpoints require a GitHub Enterprise Cloud subscription. A handful (repos, repo_*, org_* basics) work on Team or Free orgs too, but the enterprise-tier endpoints (audit log, billing, runners, Copilot, secret-scanning aggregation, members-by-consumed-license) only function for an Enterprise account. If you are not on Enterprise Cloud, you can still enable the org and repo endpoints — the enterprise ones will fail cleanly.

​
Step 1: Identify your enterprise slug

Open https://github.com signed in as a GitHub user who is an Enterprise Owner.
  1. Click your profile picture → Your enterprises
  2. Click your enterprise
  3. The URL is https://github.com/enterprises/<slug> — copy the <slug> portion
That slug is your GITHUB_ENTERPRISE_SLUG.
If you do not see Your enterprises, you are not an Enterprise Owner on any enterprise. You can still proceed using org-level endpoints only — set GITHUB_ENTERPRISE_SLUG to any non-empty placeholder (e.g. none) and skip every script whose display name begins with Enterprise.

​
Step 2: Create the Personal Access Token

ConfigView uses a classic PAT (not fine-grained) because GitHub’s enterprise endpoints, audit log, and Copilot APIs are not yet supported under fine-grained PATs.
  1. Sign in to GitHub as the Enterprise Owner identified in Step 1
  2. Open https://github.com/settings/tokens
  3. Click Generate new token → Generate new token (classic)
  4. Note: ConfigView
  5. Expiration: pick a duration that matches your secret-rotation policy (90 days, 1 year, or custom)
  6. Select scopes: check the boxes below. The scope you need depends on which endpoints you plan to enable — checking all of them is the simplest path:
  1. Click Generate token
  2. Copy the token (starts with ghp_...). You will not be able to see it again — store it somewhere safe.
SAML SSO authorization. If your enterprise enforces SAML SSO, after creating the token you must authorize it for SSO: on the token page, find the new token in the list and click Configure SSO → Authorize for your enterprise. Otherwise every API call returns 403.
Read-only scopes only. ConfigView never writes to GitHub. The scopes above let it call GET endpoints; the API has no concept of “read-only token,” so a repo scope technically allows writes — but the scripts only issue reads.

​
Step 3: Add the secrets to ConfigView

  1. Go to your ConfigView dashboard: https://{companyname}.configview.com/admin/secret/
  2. Click Add Secret and create:
    • GITHUB_TOKEN: the ghp_... token from Step 2
    • GITHUB_ENTERPRISE_SLUG: the slug from Step 1
  3. Click Save

​
Step 4: Enable the GitHub scripts in ConfigView

  1. Go to: https://{companyname}.configview.com/admin/cron/
  2. You should see github in the list of available apps
  3. Select the scripts you want to run. Group them by tier — enable only the tiers that match your plan:

​
Enterprise tier (Enterprise Cloud required)

​
Org tier (works on any GitHub Team or Enterprise org)

​
Repo tier

​
User tier

  1. Click Save
Note: ConfigView wires the parent-child dependencies automatically (e.g. org_members runs after organizations). You only need to make sure the parent script is enabled when you enable a child.

​
Step 5: Verify

  1. Go to: https://{companyname}.configview.com/admin/status/
  2. Run the GitHub health check
  3. The check should pass with your enterprise name + at least one organization listed
If a check fails:
  • 401 Bad credentials — Token expired, revoked, or has zero scopes. Re-issue from Step 2.
  • 403 Resource not accessible by personal access token — Token missing a required scope. Compare the failing endpoint against the scope table in Step 2.
  • 403 must use SAML SSO to access this resource — Authorize the token for SSO (Step 2, final note).
  • 404 Not Found on enterprise endpoints — GITHUB_ENTERPRISE_SLUG is wrong or the token’s owner is not an Enterprise Owner.
  • Org Members finds zero outside collaborators / pending invites — Frequently legitimate; the org may genuinely have none. Cross-check against https://github.com/orgs/<org>/people.

​
Data Tables

Once the scripts run, the corresponding tables are created in your database. All tables include a run_at column for historical tracking. Selected highlights below — see manifest.json for the full list.

​
What you can’t ingest with this setup

  • Private repo file contents. ConfigView reads metadata, not source. No commits, no blobs, no diffs.
  • Issue / PR bodies. Not in scope. Add via custom query if needed.
  • Actions workflow runs / job logs. Available via API but not wired in — open a feature request if useful.
  • Audit log older than 30 days. GitHub retains 180 days but the API streams it lazily; the script pulls a rolling 30-day window. Cumulative history accumulates from successive runs in run_at.