Connect
This guide walks you through connecting your GitHub Enterprise account to Zluri using a Personal Access Token (classic). This integration enables identity discovery, repository visibility, license tracking (e.g., GitHub Copilot), and more.
Prerequisites
- GitHub Enterprise Admin access
- Access to create a Personal Access Token (classic)
- Enterprise Name
- (Optional) Organization names to limit data to specific orgs
- Admin access to Zluri
Step 1: Generate GitHub Personal Access Token
-
Log in to GitHub Enterprise.
-
Go to Settings → Developer Settings → Personal Access Tokens → Tokens (classic).
-
Click Generate new token (classic).
-
Enter a token name and set an expiration.
-
Under Select Scopes, check:
read:enterpriseread:orgmanage_billing:copilot(optional, to access GitHub Copilot license data)
-
Click Generate Token and copy it immediately.
This token will not be visible again.
Step 2: Find Your GitHub Enterprise Name
- Click your profile icon in the top-right corner.
- Go to Settings → Enterprises.
- Copy the Enterprise Name shown.
Step 3: Connect GitHub Enterprise in Zluri
- Go to Sources → Integrations → Browse Catalog in Zluri.
- Search for GitHub Enterprise and click ➕ Connect.
Step 4: Review Required Scopes in Zluri
- Zluri will show the required scopes.
- Click the arrow next to each scope to view what it does.
- Click Continue.
Step 5: Enter Connection Details
-
In the form, enter:
-
Click Connect.
Step 6: Finalize the Setup
- Enter a connection name and optional description.
- Click Save.
- Zluri will validate and start syncing GitHub Enterprise data.
Notes
- The Personal Access Token must be classic (not fine-grained).
- If GitHub Copilot license data is required, make sure
manage_billing:copilotis enabled. - Ensure scopes selected in GitHub match what Zluri requires.
- If token expires or is revoked, you’ll need to regenerate and reconnect.
Updated about 5 hours ago
