Note: If your enterprise uses Enterprise Managed Users, you must follow a different process to configure SAML single sign-on. For more information, see "Configuring SAML single sign-on for Enterprise Managed Users."
Enterprise Cloud
English
Â
Enterprise administrators
Enterprise Cloud
English
Â
Managing identity and access for your enterprise
You can centrally manage access to your enterprise's resources on GitHub Enterprise Cloud with SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM).
About identity and access management for your enterprise→
You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access to organizations owned by your enterprise on GitHub.com.
Configuring SAML single sign-on for your enterprise→
You can control and secure access to resources like repositories, issues, and pull requests within your enterprise's organizations by enforcing SAML single sign-on (SSO) through your identity provider (IdP).
Managing team synchronization for organizations in your enterprise→
You can enable team synchronization between an identity provider (IdP) and GitHub Enterprise Cloud to allow organizations owned by your enterprise account to manage team membership through IdP groups.
Configuring SAML single sign-on for your enterprise using Okta→
You can use Security Assertion Markup Language (SAML) single sign-on (SSO) with Okta to automatically manage access to your enterprise account on GitHub Enterprise Cloud.
Switching your SAML configuration from an organization to an enterprise account→
Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
Help us make these docs great!
All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
Make a contribution