How to revert from Okta SSO to Google Auth after deleting SAML config?

I understand this is a frustrating situation! When you delete a SAML SSO configuration, there can be some lingering settings that cause newly invited users to still be created as SSO users instead of regular users who can use Google Auth or email/password login.

Here's what's likely happening and how to fix it:

The Issue

When SAML SSO is configured for an organization in Sanity, it becomes the default authentication method. Even after deleting the SAML configuration, the organization may still have SSO as the preferred login method, which is why new invites are creating SSO users.

How to Fix It

1. Check Organization Settings: Go to Sanity Manage and navigate to your organization's settings. Look for any remaining SSO-related settings under Settings → SAML SSO or authentication preferences. Make sure everything related to SAML is fully disabled/removed.

2. Contact Sanity Support: Since SAML SSO is an enterprise feature available on Business and Enterprise plans, some aspects of the configuration may require support intervention to fully reset. Reach out to Sanity support through the help menu in Manage or via email - they can verify that all SSO settings are completely removed from your organization.

3. Re-invite Users: Once the SSO configuration is fully cleared, you'll need to re-invite the affected users. The new invitations should create standard user accounts that can authenticate via Google Auth or other standard methods.

Why This Happens

SAML SSO in Sanity works at the organization level and changes how users are provisioned. When enabled, it becomes the primary authentication method and can affect how user accounts are created even after the configuration appears to be removed from the UI.

The support team should be able to quickly verify your organization's authentication settings and ensure everything is properly reverted to standard authentication methods. They deal with these types of configuration reversals regularly and can make sure there are no hidden settings causing the issue.