Lost access to existing Supabase project - Project Ref available (Need help recovering access)

[levisousals-arch]

Lost access to my own Supabase project (Project Ref available)

Hello Supabase team,

I'm trying to recover access to a Supabase project that I created several months ago.

Project information

Project Ref

vfyarawrpvcioryisicr

Project URL

https://vfyarawrpvcioryisicr.supabase.co

---

Background

The project is called PulseiraCheck and is a production application that I've been developing for several months.

The frontend, GitHub repository, local source code, .env, and supabase/config.toml are all intact.

Both configuration files point to the same project.

supabase/config.toml

project_id = "vfyarawrpvcioryisicr"

.env

VITE_SUPABASE_PROJECT_ID=vfyarawrpvcioryisicr

The project was originally created using GitHub authentication.

GitHub account: levisousals-arch

GitHub email: levisousa.ls@gmail.com

I can still successfully log in to Supabase using this GitHub account.

---

Current problem

When I run:

npx supabase projects list

I only see my other projects.

When I run:

npx supabase link --project-ref vfyarawrpvcioryisicr

I receive:

Your account does not have the necessary privileges to access this endpoint

If I open the project URL in the dashboard, I receive:

You do not have access to this project

I also tried the password recovery process.

Supabase confirmed by email that this account is linked to GitHub and therefore can only authenticate through GitHub, confirming that I am using the correct authentication method.

---

What I have already verified

• The GitHub account is the original account used to create the project.
• The GitHub repositories are still available.
• The local project still references the same Supabase Project Ref.
• The application source code is intact.
• I can successfully authenticate with GitHub, but I cannot access this specific project.

---

My questions

Could someone please verify:

1. Does this project still exist?
2. Which organization currently owns it?
3. Is it still associated with my GitHub account?
4. Is there any way to restore my access?

I can provide additional information privately if needed to verify ownership of the project.

Thank you very much for your time and assistance.

[GaryAustin1]

You need to file a support request, no one from Github will be able to see your account.

If it existed less than 24 hours ago check the audit log in Account Settings (upper right of dashboard under your avatar).

Do you have any other supabase accounts? Was it created in Lovable/Bolt/Vercel?
Any team members on that org that might have transferred it?

[levisousals-arch]

Thank you for your reply.

To answer your questions:

• Yes, I have other Supabase projects, but they belong to the same GitHub account and are still accessible.

• This project was created while developing my application in Lovable and connected to my own Supabase project.

• I was the only developer working on this project. There were no team members who could have transferred ownership.

Unfortunately, I cannot find the project in my dashboard anymore, even though my local application, .env, and supabase/config.toml still reference the same Project Ref.

I'm on the Free plan and I couldn't find a way to submit a support request for an account/project recovery issue.

Could you please point me to the correct support channel for this type of request?

Thank you very much for your help.

[GaryAustin1]

Is the org still there?

[levisousals-arch]

When I sign in with my GitHub account and follow the Contact Support link, Supabase redirects me to the "Create a new organization" page instead of showing any existing organization.

So it looks like my account currently has no organizations associated with it, even though my local project still points to the existing Project Ref vfyarawrpvcioryisicr.

Does this indicate that the original organization was removed or that my account lost access to it?

[GaryAustin1]

If you don't have any organziations then this says that github account is not likely where you created it. It probably created a new supabase account with that email (from the Github primary email). So no orgs here:

Normally Supabase sends emails with security info and updates (or pause warnings)... check your email for what email it was sent to.

Likely this project was created with a different email or in Vercel/Bolt/Lovable.

Does the project still work? If not then it could also have been deleted. If less than a day you can check the Audit log under your Account settings (top right avatar).

[levisousals-arch]

Thank you.

That's interesting because I still have the original project source code, the original .env, and the supabase/config.toml, and they all point to the same Project Ref (vfyarawrpvcioryisicr).

The project was developed in Lovable, and I'm now trying to determine whether Lovable created or connected the Supabase project using a different Supabase account or organization.

I'll investigate that possibility as well.

Thank you again for your help.

[GaryAustin1]

If it was Lovable cloud then there is no Supabase account for it and has to be accessed from Lovable dashboard.

[VectorPeak]

The project ref is enough for Supabase support to locate it, but the owning org / membership state can’t be confirmed from a public GitHub Discussion. If the support flow requires an org and your account currently has none, create a temporary/free org just to get access to the support form, then open an account/project ownership ticket with the project ref vfyarawrpvcioryisicr.

Include the following in the ticket: project ref, project URL, GitHub username, GitHub email, approximate creation date, Lovable involvement, and screenshots of the dashboard access error + CLI error. Don’t post service role keys or database credentials publicly.

One thing worth checking locally before filing: make sure the CLI is not using an old access token from a different Supabase account.

npx supabase logout
npx supabase login
npx supabase projects list

Also, if Lovable provisioned or managed the Supabase project at any point, contact Lovable support too. Supabase project ownership is tied to a Supabase organization, not to the GitHub repo or the presence of the project ref in .env / config.toml.