Project missing from dashboard — "Not a member of the selected organization"

[awuestenfeld]

My project no longer appears in my dashboard, but it's still live and serving traffic.

• Project ref: ominwpxvdjzoflmibvjo
• Support ticket: SU-476158
• Plan: Free

What happened: I couldn't sign in with my usual credentials this morning. I signed in with GitHub instead, which worked, but my dashboard now shows "Your organizations" with no organizations listed. The project was previously under an org named "Game Day Skinz Inc". I am the sole owner and no one else has ever had access.

The project itself is fine — I can query the REST API right now and get data back, and my application is running normally against it. This is purely dashboard/account access.

Trying to file a support ticket through the dashboard form fails with "Failed to submit support ticket: Not a member of the selected organization", which suggests my account has been detached from the org rather than the project being deleted.

I have not created a new organization, in case that would complicate reattaching the existing one.

Can someone point me at how to get my account reattached to the org that owns this project?

[GaryAustin1]

Then you are almost certainly in the wrong dashboard or the project was created thru vercel/lovable/bolt.
A lesser thing that comes up is you have team members on the org and one dropped you.

Check your past emails from Supabase and use the exact same login method (if Github the primary email must match).

support@supabase.com otherwise. The account security group though is taking well over a week so you should really work to find the correct account for the project. It will not be running if not in an account somewhere.

[awuestenfeld]

To clarify: I signed up originally with my personal email. This morning that login failed, so I signed in with GitHub, which uses the same address but is evidently a separate identity — that's the empty account I'm in now. So the org is likely still on the email-based account, and my actual problem is getting back into that one rather than a detached org.

[GaryAustin1]

I would try chatGPT login with a chatGPT account using the email you have verified is correct by looking at past emails from Supabase for the project. The project must have been created in supabase.com and not in lovable/bolt/vercel.
Otherwise that email is only way to get help and it will be awhile.

[awuestenfeld]

Correct, it was set up directly in Supabase

[GaryAustin1]

If you are using the correct email the chatGPT login will work. Has for many since it was added to get in to lost Github and lost password email account situations. If it does not work then very highly likely you are not using the correct email.

[awuestenfeld]

Thanks. It didn't work. I've confirmed the email used at sign up and it hasn't changed (heck I even received a 'Supa Update' email just the other day). Thank you for the assistance!

[awuestenfeld]

I know the odds of this getting fixed while being on the free plan is slim to none, any other ideas out there?

[safshargh]

I’m experiencing what appears to be the same issue.

My existing Supabase organisation/project has disappeared from the dashboard, while the application/backend itself still exists and continues to be referenced by my app.

I can authenticate successfully with the correct GitHub account, but Supabase now redirects me to /dashboard/organizations and prompts me to create a new organisation.

I have already completed browser/cache/incognito troubleshooting and verified my GitHub/Supabase identity.

I opened support ticket SU-475662 several days ago and have still not received a substantive response.

The dashboard support form also cannot be submitted because it requires me to select the organisation that has disappeared.

This is now blocking active development of my application.

If a Supabase moderator is able to bump SU-475662 internally to the appropriate account/platform team, I would really appreciate it.

I can provide project/account verification privately to Support.

Thanks.

[felipe-teo]

Your symptom (empty org list right after switching to GitHub login) almost always means GitHub sign-in created a brand-new empty Supabase account, and your real org is still under the email identity. While support catches up: since your REST API is answering, your connection string still works, so you can pg_dump everything to a new project you own today and stop depending on the ticket. Happy to show you both paths in 20 min, no charge.

[safshargh]

Thanks — that diagnosis certainly seems consistent with what I’m seeing.My Supabase Audit Logs show a new user profile being created on 15 September immediately before this issue appeared, while my existing application/backend has continued operating.For now I would prefer not to migrate or create a replacement project because this is an active application and I don’t want to introduce Auth, RLS, Storage, Edge Function or configuration issues unnecessarily.Ideally I’d like Supabase to restore/reassociate my existing JourneyJournal organisation/project with the correct account.My support ticket is SU-475662.If you’ve seen Supabase resolve this specific identity/account-mapping issue before, I’d be very interested to know what they did or whether there is a Supabase issue/discussion documenting the fix.Thanks for the offer to help.On 23 Sep 2026, at 5:41 pm, felipe-teo ***@***.***> wrote: Your symptom (empty org list right after switching to GitHub login) almost always means GitHub sign-in created a brand-new empty Supabase account, and your real org is still under the email identity. While support catches up: since your REST API is answering, your connection string still works, so you can pg_dump everything to a new project you own today and stop depending on the ticket. Happy to show you both paths in 20 min, no charge. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[felipe-teo]

Makes sense to keep the active project in place. On the reassociation path: the fix Supabase applies here is on their side — they merge the empty GitHub-created account into your original org, or move the org's ownership to the identity you're now logging in with. Only their support can do it; from the outside no one can reassign org ownership. Two things that speed up ticket SU-475662: (1) reply with your org ID, the project ref, and the exact email/identity that owns the working project, so they can map it without back-and-forth; (2) point them to the audit-log line showing the 15 Sep profile creation — that's the evidence they need. If it drags past a few days and you want a fully-owned backup as insurance without touching the live app, I can set that up read-only so nothing changes on production. Glad the diagnosis helped.

[safshargh]

Thanks — that’s very helpful. I’ll now provide Supabase Support with the project ref, current identity and the 15 Sep audit-log profile creation event. I don’t have the org ID because the organisation is no longer visible in my dashboard, so I’ve asked them to identify it from the project ref. I’ll hold off on any migration/backup changes for now while they investigate.On 23 Sep 2026, at 7:49 pm, felipe-teo ***@***.***> wrote: Makes sense to keep the active project in place. On the reassociation path: the fix Supabase applies here is on their side — they merge the empty GitHub-created account into your original org, or move the org's ownership to the identity you're now logging in with. Only their support can do it; from the outside no one can reassign org ownership. Two things that speed up ticket SU-475662: (1) reply with your org ID, the project ref, and the exact email/identity that owns the working project, so they can map it without back-and-forth; (2) point them to the audit-log line showing the 15 Sep profile creation — that's the evidence they need. If it drags past a few days and you want a fully-owned backup as insurance without touching the live app, I can set that up read-only so nothing changes on production. Glad the diagnosis helped. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[felipe-teo]

You don't strictly need the org ID — Supabase Support can locate the org from the project ref alone, so lead with the ref plus the 15 Sep audit-log profile-creation event and the email/identity you're logging in with now. If you want it anyway, the org ID is in the dashboard URL when you're inside the org (app.supabase.com/org//…). One phrasing that speeds these up: ask them explicitly to "re-map project to the account with email X" so a human doesn't have to infer your intent. If it stalls more than a couple of days, happy to hop on a short call and sort it live — but writing works fine too, and keeps a record. Let me know how support responds.

[safshargh]

Thanks Felipe — really appreciate the guidance.I’ve now gone back to Supabase Support and explicitly asked them to re-map project gcalmpaujshxqrhjdboe to ***@***.*** / safshargh identity, and I’ve pointed them again to the 15 Sep profile-creation audit event.The main frustration at this point is the lack of response. This issue is actively holding up development of my app, and I’ve already had the ticket open for several days without a substantive update.From your experience, is there a more efficient way to get this in front of the right Supabase account/platform team? For example, is there a particular GitHub discussion, Discord channel, moderator, escalation path, or wording that tends to get these identity/organisation-mapping issues looked at more quickly?I’m happy to keep everything in writing and provide whatever verification they need — I’m mainly trying to avoid losing more development time waiting for the ticket to be picked up.Thanks again for your help.On 24 Sep 2026, at 4:02 pm, felipe-teo ***@***.***> wrote: You don't strictly need the org ID — Supabase Support can locate the org from the project ref alone, so lead with the ref plus the 15 Sep audit-log profile-creation event and the email/identity you're logging in with now. If you want it anyway, the org ID is in the dashboard URL when you're inside the org (app.supabase.com/org//…). One phrasing that speeds these up: ask them explicitly to "re-map project to the account with email X" so a human doesn't have to infer your intent. If it stalls more than a couple of days, happy to hop on a short call and sort it live — but writing works fine too, and keeps a record. Let me know how support responds. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[safshargh]

@GaryAustin1 sorry to tag you directly, but I’m hoping you may be able to help escalate this.
My Supabase support ticket SU-475662 has now been open since 16 September and I still have not received a response.
The issue is account-specific and can only be fixed by Supabase: my existing JourneyJournal organisation/project is still operational, but it has disappeared from my dashboard after a new profile was created on 15 September.
Project ref: gcalmpaujshxqrhjdboe
I’ve already provided Support with:

• the project reference
• my current GitHub/Supabase identity
• the 15 Sep audit-log profile-creation event
• screenshots confirming the empty organisation dashboard
• an explicit request to re-map the existing project/organisation to my account
  This has now been unresolved for nearly two weeks and is actively holding up development of my application.
  If you still have an internal path to bump account-access tickets, I would really appreciate SU-475662 being raised with the appropriate Supabase account/platform team.

Thanks for any help you can provide!!