Corma
Book a callBlog
  • Get started - Setup & implementation
  • Concepts and use cases
    • On & Off boarding
      • Define app owners
      • Create app bundles
      • Onboard a user
      • Offboard a user
      • Track provisioning progress
    • Expenses
      • CSV expense import
      • Inserting expense data manually
      • OCR Expense import
      • Contract Management & License Status Breakdown
    • Discovering Shadow IT
    • Access Requests
    • Employee view
    • Adding Applications to Corma
    • Licenses
    • App Analytics
  • The browser extensions
    • How to deploy Corma extensions with Google admin console
    • How to deploy Corma extensions with Microsoft intune
    • How to deploy extensions using GPO
    • How to manually install the Corma extension and login
    • How to deploy Corma extensions with Jamf
  • Integrations
    • Identity and Access Management
      • Google workspace
      • Microsoft Entra ID
      • Okta
    • Finance and accounting
      • Pennylane
      • Spendesk
      • Qonto
      • Candis
    • HRIS
      • Factorial
      • Personio
      • Lucca
      • Payfit
      • BambooHR
      • Deel
      • Hibob
      • Rippling
      • Workday
    • SaaS applications
      • Slack
      • Atlassian
      • Miro
      • Notion
      • LastPass
        • LastPass connection tutorial
        • LastPass Audit Log Collection
      • 1Password
      • Github Enterprise
      • Aircall
      • Hubspot
      • Salesforce
      • Intercom
      • Zendesk
      • Figma
      • Adobe
      • Canva
      • Asana
      • Front
  • General documentation
    • What is Corma?
    • General tech information
    • The Corma Glossary
    • Corma Product Roadmap
  • Security
  • Helpdesk
  • Changelog
Powered by GitBook
On this page
  • 1. On your Corma app go to the integrations page
  • 2. Under "Direct SaaS integrations" click on "Connect" for Github
  • 3. Go to your personal settings to generate an admin token
  • 4. Generate the token with the correct scopes and insert it in Corma
  • 5. Enter your Github organization name in Corma and click "Submit"
  • 6. You've successfully connected Github to Corma!
  1. Integrations
  2. SaaS applications

Github Enterprise

Previous1PasswordNextAircall

Last updated 1 month ago

An admin access to Github is required to connect Github to Corma

A Github Entreprise company account is neccessary for this integration to work

1. On your Corma app go to the integrations page

2. Under "Direct SaaS integrations" click on "Connect" for Github

3. Go to your personal settings to generate an admin token

As an Enterprise Organization admin, in Github go to on your profile then :

Settings > Developer settings > Personal access tokens

4. Generate the token with the correct scopes and insert it in Corma

Once on tokens page, click the button

[ Create new token (classic) ]

For expiration : No expiration is the best option to maintain Corma connection.

5. Enter your Github organization name in Corma and click "Submit"

https://github.com/[ORG NAME]

6. You've successfully connected Github to Corma!

Data should be synchronized within the next 24 hours and will be synched every day to your Corma app.

For scopes, we need the followings :

  • repo:status

  • repo_deployment

  • public_repo

  • read:org

  • notifications

  • read:user

  • user:email

  • read:discussion

  • read:enterprise

  • read:audit_log

  • read:project

This is the official Github name of your Organization. You can find it on your . Just copy-paste it from here, or from the URL when clicking on it.

⚠️
organizations list page
www.app.corma.io/integrations
Click on Settings on the right side bar
Att the bottom left click on "Developer settings"
Navigate to : Personal access token > Tokens (classic)
Make sure you've selected all the right scopes