The Wayback Machine - https://web.archive.org/web/20200725091203/https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on

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

Ask a human

Can't find what you're looking for?

Contact us