← Back to Archive
Thread ID: 6960B1B4

supabase Subject: Request to change connected Supabase projectHello Lovable Support Team

Archived from community support channel. Created 1/9/2026
OP
Hello Lovable Support Team I'm having issues with the Lovable + Supabase integration after deleting my original Supabase project. Context: The original Supabase project was deleted. I created a new Supabase project. In Lovable → Connectors → Supabase the status shows Enabled (organization-level connection). However, the app does not behave as if it's properly connected to the new Supabase project. What I've done: Manually created required tables in the new Supabase project (including user_roles). Verified my user exists in Auth → Users. Added myself as admin in public.user_roles using the correct auth.users.id. Configured RLS policies. Cleared browser storage and tested in Incognito. Problems: Admin role is not detected by Lovable Admin UI options do not appear at all. Auth/session behavior is inconsistent Sometimes auto-login occurs and logout fails with an error.
P
(edited)
M
URGENT / PROJECT BLOCKER The Lovable AI bot is telling me to create a new project and lose dozens of hours of work, because I can't reconnect my app to Supabase after deleting the old project. This is not a user-side issue: The Supabase binding is locked at the Lovable Cloud / backend level .env and supabase/config.toml are automatically restored after deletion Project remix changes NOTHING There is no way to manually reset the integration As a result, I don't have admin rights, can't access the admin section, and can't add or edit real attractions This completely blocks development. I need: a manual full detach / reset of the Supabase binding on the Lovable side or human intervention from the team, not another bot response Can someone from the team please take a real look at this?
M
URGENT / PROJECT BLOCKER

Ready to Take The Next Step? Let’s Chat!

BOOK A CALL →

enrollments@ambitiouslabs.io
+1 469-402-6327