Requesting Access
If you're an Atea employee, access can be ordered through OneHub.
If the direct link does not work, search for "GitHub Enterprise Cloud" or go to "Access, Accounds and Licenses" -> "System or Application". Access will be automatically granted after your manager has approved the request. You should receive two e-mails: 'Approved' and 'Complete' - make sure you received both e-mails. Might take some minutes, in rare case up to some hours, from completed request, to M365 user account is synchronized. If it doesn't work right away after approval, just wait a bit and try again.
Private GitHub account
If you don't already have a private GitHub-account, create one. Make sure you add your full name in the account, add 2FA (multi factor authentication), and add & verify your Atea-mail (if you use private mail for your GitHub account).
Connect your GitHub account to Atea's GitHub
After your OneHub request has been approved and completed, and the change has been synced to M365, you should automatically receive an invite to your Atea email, asking you to join the "atea" GitHub organization (the sync only happens once every 40 minutes). The invitation should be sent from the atea-asa GitHub user. Follow the proceedures in that email. The invite is only valid for two weeks, and if it expires, you have to sign in to your GitHub account, and then go to the SAML SSO url to connect your GitHub account.
FAQ
Non-Atea employee, but need access?
If you're not an Atea employee, and you require access, please request through your contact at Atea.
Questions? Need help?
Join our Teams group