October 2026 release is live Read More
Breadcrumbs

GitHub Enterprise Onboarding

Why this matters: GitHub is licensed per seat at the enterprise level, but seat count alone doesn't tell you whether it's actually being used, or by whom. Connecting your GitHub Enterprise account here brings usage and cost into Mavvrik's SaaS Cost dashboards, alongside the rest of you spend.

Currently, only GitHub Enterprise Cloud accounts at the enterprise level are supported.

Before onboarding your GitHub Enterprise Cloud account, log in to http://github.com as an Enterprise Admin and follow the steps below.

Configuration steps

Step 1: Create a Personal Access Token

GitHub billing usage endpoints do not support fine-grained personal access tokens (PATs).

For more information, see the GitHub REST API Prerequisites documentation.

  1. Login to http://github.com as Enterprise Admin

  2. Go to Profile → Settings → Developer Settings → Personal access tokens (classic)

  3. Click Generate new token (classic)

  4. Fill in the token details:

    • Set Note to mavvrik-github

    • Set Expiration as per your organization's security policy

    • Select the following scopes: read:enterprise, read:org, read:user

  5. Click Generate token and copy it; you will not be able to see it again

Step 2: Verify Your Organisation's Domain

Required for Mavvrik to map users to their corporate email addresses. Skip if your organisation already has a verified domain.

  1. Go to your organisation's settings on GitHub

  2. Navigate to Settings → Verified & approved domains (see GitHub documentation)

  3. Add and verify your company domain (e.g. http://yourcompany.com )

Step 3: Authorize the Token for SSO

Required for Mavvrik to fetch corporate email addresses for your users.

  1. Go to github.com/settings/tokens

  2. Find the token you just created (mavvrik-github- )

  3. Click Configure SSO next to the token

  4. Click Authorize next to your organisation name

Step 4: Get Your Enterprise Slug

Navigate to your GitHub Enterprise settings, select the enterprise account you want to connect, and copy the Enterprise Slug from the browser URL.

Example: https://github.com/enterprises/<your-enterprise-slug>

Step 5: Onboard in Mavvrik

  1. Go to the Menu

  2. Click on Admin → Accounts → SaaS

  3. Click the + Account button

  4. Select

  5. Enter Enterprise Slug & Personal Access Token

  6. Click Connect

After onboarding is completed, allow up to 24 hours for data ingestion. Once ingestion is complete, cost will be visible under SaaS > Cost.

Troubleshooting

  • If the account does not connect, verify the token and enterprise slug entered in Mavvrik.

  • If authorization fails, confirm that the token is authorized for SSO and has the permissions described above.

FAQs

Does this work with GitHub Enterprise Server or non-Enterprise plans?

No, only GitHub Enterprise Cloud accounts at the enterprise level are currently supported.

Do I need to verify my organization's domain every time?

No, domain verification is only required so Mavvrik can map users to their corporate email addresses. Skip that step if your organization's domain is already verified.

How is GitHub Copilot billed?

As of June 1, 2026, GitHub uses usage-based billing. Each plan includes a monthly allowance of GitHub AI Credits, and usage is measured by the tokens an interaction consumes, priced per model, at one cent per credit. For Business and Enterprise, those credits are pooled across the organization, and usage past the pool bills as overage.

What happens when Copilot AI Credits run out?

If additional usage is allowed, keeps working and the extra usage bills as overage at the published per-credit rate. If it is not allowed, stops until the next cycle. Either way, overage is where the unplanned cost shows up, which is why attributing it matters.

What does Mavvrik's GitHub Copilot integration do?

It brings GitHub cost and usage data into Mavvrik, including overage spend, and makes it analyzable by user, team, cost center, account, model, operation, usage type, quantity, rate, and total cost. Engineering, FinOps, and finance work from the same data instead of reconciling the bill by hand.

Can I attribute Copilot cost to a team or cost center?

Yes. Mavvrik attributes spend, overage included, to team and cost center alongside user, account, model, and operation, which is what finance and FinOps need for allocation, showback, and chargeback.

Does Mavvrik replace GitHub billing?

No. GitHub remains the billing and product source. Mavvrik adds attribution, reporting, allocation, investigation, and governance on top of spend.