Lost dashboard access to all Supabase projects after a service disruption

[polluxchou]

Hi everyone,

After a recent Supabase service disruption or period of instability, I suddenly lost access to all of my existing projects in the Supabase Dashboard.

When I try to open any project, I receive the following error:

You do not have access to this project.

I am then redirected to the “Create a new organization” page, as though my account is no longer a member of any organization.

Current situation

• I have lost dashboard access to four projects.
• I previously had owner/admin access to these projects.
• The projects and databases are still running normally.
• Existing applications are still serving production traffic through their current API keys.
• The issue appears to affect only dashboard access, organization membership, or project permissions.

Because of this, I can no longer:

• Run SQL queries
• Apply migrations
• Change project settings
• Manage API keys
• Perform administrative operations
• Respond properly to production incidents

I have confirmed that I am signing in using the same authentication method and account that previously had access.

Questions

1. Has anyone experienced organization membership or project ownership disappearing after a service disruption?
2. Are there any account recovery or organization membership checks I can perform myself?
3. Is Supabase Support the only team that can restore owner/admin access in this situation?

I have already submitted a support request, but I am posting here to find out whether this is a known issue or whether other users have experienced something similar.

Thanks for any guidance.

[Samielakkad]

Because all four projects are still serving traffic, this looks like a Dashboard identity or organization-membership problem rather than project deletion.

I would check these in order:

1. Open the Dashboard in a private/incognito window and sign in using the exact same provider as before (email/password, GitHub, Google, or SSO). Supabase documents that email/password and SSO identities can be treated as different accounts even when they use the same email address: https://supabase.com/docs/guides/troubleshooting/sso-error-you-do-not-have-permissions-to-join-this-organization-or-prompts-to-create-new-organization
2. Clear the Dashboard cookies/cache or try another current browser. This is Supabase's documented first step when projects stop loading in the Dashboard: https://supabase.com/docs/guides/troubleshooting/supabase-dashboard-not-loading-project-not-loading-on-dashboard-LfMq9F
3. If the organization has another owner, ask them to check Organization > Team. They can confirm whether your original identity is still listed and re-invite or restore the appropriate role. Supabase's role documentation is here: https://supabase.com/docs/guides/platform/access-control
4. If you already have a Management API access token from before the incident, use it only to gather evidence such as the organization/project references visible to that token. Do not publish the token or any service-role keys.

If the same identity is no longer an organization member and there is no second owner who can restore it, Support is the correct escalation. A community member cannot safely recreate that membership. Add the following to the existing ticket so Support can correlate it quickly:

• all four project references and the organization ID, if known;
• the exact login provider and account email used before and after the incident;
• the approximate time access disappeared;
• a screenshot of the redirect and error;
• confirmation that the data plane is healthy while only Dashboard access is missing;
• any incident/status-page reference that coincides with the loss of access.

I would not create replacement projects, rotate working keys, or attempt a project transfer while ownership is unclear. Those actions do not repair the organization membership and could make recovery harder. Supabase also recommends having more than one organization owner for production projects so there is a recovery path if one identity loses access: https://supabase.com/docs/guides/deployment/going-into-prod