Guides
One page per error, task and builder tool.
Tables, checkers and free downloads
- Free migration template and grants auditTwo .sql files. One creates a table the right way. One shows what every table grants today.
- Which grant does each call need?Tick what your code does. Copy the smallest grant that makes it work.
- Postgres ACL decoderPaste the privilege string. Get one row per role, in words.
- 42501, PGRST205, 42P01: which error is yours?Match the code in the response. See its HTTP status and whether a grant is the fix.
- All 30 Supabase advisor lintsName, level and one-line summary for every lint, 0001 to 0030.
- Which policy does each command need?One table: every command against the policies Postgres checks for it.
- Which role does each Supabase key use?The key picks the Postgres role. The role needs the grant.
Errors and tasks
- 42501: permission denied for tableThe role has no grant on the table. Paste the error or your table and get the SQL.
- Supabase table not exposed to the Data APIA new table is invisible to the API until a role is granted access. Here is the grant.
- New Supabase table not showing in the APITwo checks tell you if the grant is missing. Then fix it below.
- The Supabase change of 30 October 2026New tables in public need explicit grants. Dates, scope and the SQL in one place.
- Every cause of 42501 on Supabase42501 means "insufficient privilege". Match your message to a row.
- Grants for anon, authenticated and service_roleThree roles, four privileges. This is the grid the tool fills in.
- Is my Supabase project affected?Run one query. No rows means new tables get no grants.
- Grants vs row level securityTwo checks run on every request. A grant comes first.
- "Grant the required privileges to the current role with: GRANT ..."The hint names one missing grant. Paste it and get the full set.
- permission denied for sequenceThe table is granted and its id counter is not. One more grant fixes it.
- Go back to automatic exposureSupabase documents the SQL. Read what it re-opens before you run it.
- Public read-only tableAnyone reads. Only your server writes. Here is the SQL.
- Owner-only tableEach signed-in user sees and changes only their own rows.
- Private, server-only tableNo access from the browser. Your server reads and writes.
- Check the grants on a tableOne query lists every role and privilege on a table.
- Local tables missing grants after db resetA reset replays your migrations. Without grants in them, tables come back closed.
- service_role gets "permission denied for table"The secret key skips policies. It does not skip grants. Add one line.
- Prisma tables return "permission denied for table"Prisma made the table, so the API roles were never granted. Here is the proof and the fix.
- Permission denied for schema publicThe role cannot enter the schema, so table grants never get looked at.
- Permission denied for viewA view has its own grants. With security_invoker, its tables need them too.
- Permission denied for functionSomeone revoked execute. Grant it back to the roles that call the function.
Builder tools
- Lovable app says "permission denied for table"The new table has no grants. Paste it below and copy a fix prompt made for Lovable.
- Bolt app says "permission denied for table"The new table has no grants. Paste it below and copy a fix prompt made for Bolt.
- Replit app says "permission denied for table"The new table has no grants. Paste it below and copy a fix prompt made for Replit.