Account still inaccessible after escalation — “User’s profile not found” [SU-416784, follow-up to #47859]

I am opening a new issue because my previous issue, #47859, was closed even though the underlying account access problem was never resolved.

I have been unable to access my Supabase dashboard and client project for several weeks.

Every login attempt still results in:

Failed to retrieve account information Error: User's profile not found

Supabase Support informed me on July 20 that this case had been escalated to the Auth team under support reference:

SU-416784

It is now August 7, and I still have not received a resolution or meaningful update regarding the escalation.

Previous issue

Previous GitHub issue:

#47859 — Supabase login fails with “User’s profile not found” after GitHub/email identity mismatch

The issue was later closed for inactivity even though my account remained inaccessible. I commented afterward confirming that the issue was still unresolved, but I have still not received a recovery path.

What I have already tried

I have already completed the troubleshooting previously suggested, including:

• Signing in through my original GitHub account
• Restoring the original university email as the primary and verified GitHub email
• Signing out and back in
• Clearing browser cookies and cache
• Using incognito/private browsing
• Trying different Supabase login methods
• Reviewing my GitHub email and identity settings

None of these steps resolved the issue.

I still receive:

Failed to retrieve account information Error: User's profile not found

Based on the behavior, authentication appears to succeed, but the Supabase Dashboard is unable to retrieve the profile associated with the authentication identity.

This therefore appears to require Supabase-side inspection of the account/profile mapping, rather than additional browser troubleshooting.

Time-sensitive account concern

My account was originally associated with a university email address that I will eventually lose access to.

I changed my GitHub primary email because I need to transition to a permanent personal email, but I currently cannot access the Supabase dashboard to properly manage or migrate the account.

I need assistance safely moving the account to my permanent email without losing access to the existing organization or client project.

I am also prepared to upgrade to Supabase Pro, but I cannot reasonably upgrade or manage billing while I am completely locked out of the account.

Impact

The affected Supabase project contains client data, and I currently cannot access the dashboard to manage the project.

This has now been unresolved for several weeks despite an existing support escalation.

Request

Could someone from the Supabase team please take ownership of this case and inspect the account state directly?

Specifically, I would appreciate help with:

1. Checking the Supabase dashboard profile currently associated with my authentication identity.
2. Determining whether the GitHub/auth identity and dashboard profile became disconnected.
3. Restoring or relinking the profile if necessary.
4. Recovering access to the existing organization/project.
5. Safely migrating the account from my university email to my permanent personal email.
6. Confirming the current status of support escalation SU-416784.

I can provide the following privately through the existing support thread:

• Original university email
• New personal email
• GitHub username/account details
• Affected project reference
• Organization information
• Screenshots
• Any additional ownership verification required

I am happy to complete any verification immediately.

At this point, I am specifically requesting escalation to someone who can inspect or repair the account/profile state on Supabase’s side.

Please do not close this issue as resolved/completed unless access to the account has actually been restored or a concrete recovery path has been provided.

Thank you.