GitHub · GH-100
Managed users and personal accounts
GH-100 · Lesson 1 of 17 · 3:57
YouTube loads only after you press play. Watch on YouTube ↗
In this lesson
Prepare for the GH-100 exam (GitHub Administration). In this lesson: the two enterprise types on GitHub Enterprise Cloud (personal accounts with optional SAML, or Enterprise Managed Users provisioned by your identity provider), what managed user accounts can and cannot do, data residency on GHE.com, how GitHub authenticates people, Git, the API, and apps, SSO authorization of tokens and SSH keys, and how roles stack from the enterprise to the repository. Includes three original practice questions.
Preview the topics
- Contoso’s European subsidiary must keep its code and data in the EU, without running its own servers, and its developers must never publish public repositories with company accounts. Which setup fits?
- A Contoso engineer’s classic personal access token works on other organizations, but cloning a repository of the powertrain organization, which enforces SAML single sign-on, fails. What’s missing?
- Contoso’s open source office wants engineers to keep contributing to public projects with the same account they use for company code, while Entra ID still controls access to company organizations. Which setup fits?