Managing bots and service accounts with SAML single sign-on

Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.

SAML single sign-on is available with GitHub Enterprise Cloud. For more information, see "GitHub's products."

To retain access for bots and service accounts, organization administrators can enable, but not enforce SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).

Note: If you enforce SAML single sign-on for your organization and do not have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.

Further reading

Did this doc help you?Privacy policy

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

Or, learn how to contribute.