When a social login provider (e.g. "Continue with Google") is disabled for an organization's domain, users who click it today hit a hard-stop "Login is disabled" page with no path forward, even though the org has a working SSO (e.g. Okta) configured. Instead, blocked social-login attempts should automatically redirect to the org's configured SSO flow, or at minimum surface an explicit "Login with SSO" button on that page. Without this, anyone following a shared link lands on a dead end before ever reaching login, which directly hurts first-time user onboarding and early retention.