You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
When attempting to log in via SSO, you may observe the message "You do not have permissions to join this organization" or be prompted to create a new organization.
Why This Happens:
Supabase treats email/password and SSO identities as distinct, even when the email addresses are identical. Existing memberships associated with email/password accounts are not automatically linked to a newly created SSO identity.
How to Resolve This Issue:
If you want your org members to auto-join:
As an organization administrator, ensure "Join organization on signup" is enabled in your SSO configuration.
Navigate to your organization's Members settings.
Remove any existing email/password-based user accounts that are intended to transition to SSO.
Instruct these users to log in via SSO; they will be automatically re-added to your organization with the default role if auto-join is active.
Alternatively, you can manually re-invite their Google SSO identity to the org, ask them to accept the invite while signed in via Google and once confirmed, remove their old email/password account.
Best Practice When Setting up SSO:
Maintain owner account with a password login as a break-glass backup.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
When attempting to log in via SSO, you may observe the message "You do not have permissions to join this organization" or be prompted to create a new organization.
Why This Happens:
Supabase treats email/password and SSO identities as distinct, even when the email addresses are identical. Existing memberships associated with email/password accounts are not automatically linked to a newly created SSO identity.
How to Resolve This Issue:
If you want your org members to auto-join:
Memberssettings.Alternatively, you can manually re-invite their Google SSO identity to the org, ask them to accept the invite while signed in via Google and once confirmed, remove their old email/password account.
Best Practice When Setting up SSO:
Maintain owner account with a password login as a break-glass backup.
All reactions