Rowpass 42501: permission denied for table Not affiliated with Supabase

Rowpass / Guides

Bolt app says "permission denied for table"

The new table has no grants. Paste it below and copy a fix prompt made for Bolt.

Write the fix for your tables

 

Waiting for a paste.

    Who can reach each table

    Your tables show up here, one row each, with a choice of who can reach them.

    The SQL appears here as soon as a table is found.

    Parsed in your browser. Your SQL is never uploaded, and no site or database is scanned.

    Why this happens in Bolt projects

    When Bolt adds a table to your Supabase database, the table lands in the public schema. Supabase used to grant every new public table to the API roles on its own. It no longer does, so the first request to the new table fails with 42501 until the grants exist.

    • Before: every new table in public was granted to anon, authenticated and service_role automatically.
    • After the change: a new table has no grants until you write them. The Data API answers 42501, permission denied for table.
    • Tables that already existed keep their grants. Row level security works as before.

    How to apply the fix from Bolt

    Bolt's Supabase help article (read 2026-11-10) does not describe how database changes are applied and does not mention grants or 42501. We could not verify Bolt's exact steps, so the dependable route is the Supabase SQL Editor. The fix prompt is still worth giving to Bolt so that future tables include their grants.

    1. Paste the table into the tool above and choose the access you want.
    2. Open the Fix prompt tab. The prompt tells the builder to add the SQL unchanged, and to include grants with every table it creates from now on.
    3. Or skip the builder: copy the GRANT + RLS tab and run it in the Supabase SQL Editor.

    What the SQL looks like

    For a table where each signed-in user sees only their own rows:

    -- public.your_table: owner only
alter table public.your_table enable row level security;
revoke all on table public.your_table from anon, authenticated;
grant select, insert, update, delete on table public.your_table to authenticated;
grant select, insert, update, delete on table public.your_table to service_role;
drop policy if exists your_table_select_own on public.your_table;
create policy your_table_select_own on public.your_table
  for select to authenticated
  using ( (select auth.uid()) = user_id );
drop policy if exists your_table_insert_own on public.your_table;
create policy your_table_insert_own on public.your_table
  for insert to authenticated
  with check ( (select auth.uid()) = user_id );
drop policy if exists your_table_update_own on public.your_table;
create policy your_table_update_own on public.your_table
  for update to authenticated
  using ( (select auth.uid()) = user_id )
  with check ( (select auth.uid()) = user_id );
drop policy if exists your_table_delete_own on public.your_table;
create policy your_table_delete_own on public.your_table
  for delete to authenticated
  using ( (select auth.uid()) = user_id );

    Dates are from the Supabase changelog post published 2026-04-28, read 2026-11-10. We have not seen an official post confirming that the 2026-10-30 step finished for every project, so check your own project with this query.

    Questions

    Will Bolt fix this by itself if I paste the error?

    It may. The error carries a hint that names one missing grant, and Supabase says tools can correct themselves from it. The hint covers one role and one privilege at a time, so you can go through several rounds. The SQL here sets every role, turns on row level security and adds the policies in one step.

    Is it safe to grant access to anon?

    Only for data that is meant to be public. A grant to anon with a policy of "using ( true )" lets every visitor read every row. Choose Owner only or Private for anything else.

    Sources

    Related

    Did it fix your error?