When a GitHub organization enables SAML SSO, what happens to members who have not yet authenticated via SAML?
Select an answer to reveal the explanation.
Short Explanation and Infographic
SAML SSO doesn't immediately boot people — it's more like a velvet rope. Non-authenticated members can still see public repos, but the private resources go dark until they link their accounts through SSO.
Full explanation below image
Full Explanation
When SAML SSO is enabled for a GitHub organization, existing members are not immediately removed. However, they lose access to private organization resources (private repositories, organization secrets, etc.) until they complete SAML authentication and link their GitHub account to their IdP identity. They can still access public repositories. Organization owners and admins receive notifications encouraging members to authenticate. If an admin wants to enforce stricter access, they can configure the organization to require SAML SSO for all members, which would limit access more aggressively. The 24-hour grace period is not an official GitHub feature.