Supabase's 30 October change: has your project switched, and what breaks
Supabase's change to new tables is due on every existing project today, 30 October 2026. Tables you already have keep working. The trouble starts the next time you, a teammate or Lovable, Bolt or Cursor creates a table, and in a few places people don't expect. Here's how to check whether your project has switched, where it breaks, and the safe fix.
Stuck on this? Get it fixed for €49.
Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.
Get it fixed for €49What changed
Until now, every new table in the public schema was automatically granted select, insert, update and delete for the anon, authenticated and service_role roles. Supabase is removing that default. New projects have worked this way since 30 May 2026, and the changelog says the change is "enforced on all projects on 2026-10-30". After that, a new table needs an explicit grant before supabase-js, the REST API or GraphQL can see it.
- Existing tables keep their grants and keep working.
- Row level security works exactly as before.
- Apps that only talk to Postgres directly (an ORM or a connection string on a server) aren't affected.
- The
storage,authandrealtimeschemas aren't affected.
Supabase gives a date but not a time, so don't assume your project switched at midnight. Check it.
1. Has your project switched yet?
Run this in the Supabase SQL editor. It shows what Postgres will give the API roles on the next table the postgres role creates in public:
select a.grantee::regrole as role,
string_agg(a.privilege_type, ', ' order by a.privilege_type) as privileges
from pg_default_acl d
cross join lateral aclexplode(d.defaclacl) a
where d.defaclrole = 'postgres'::regrole
and d.defaclnamespace = 'public'::regnamespace
and d.defaclobjtype = 'r'
and a.grantee in ('anon'::regrole, 'authenticated'::regrole, 'service_role'::regrole)
group by 1
order by 1;
If the rows still include SELECT, INSERT, UPDATE, DELETE, you're on the old behaviour for now. If those are missing, or there are no rows, new tables are closed until you grant them.
2. The places it breaks that people miss
A migration that drops and recreates a table
"Existing tables keep working" only holds while the table exists. A migration that does drop table then create table, a create table ... (like ...) copy, or restoring a table from a dump all make a new table, and a new table gets no grants. Your policies come back if the migration recreates them. The grants don't. AI tools rebuild tables like this more often than you'd think, so read the migration before you apply it.
New views
Views get the same default privileges as tables, so a new view fails with permission denied for view your_view. Grant it like a table (grant select on public.your_view to authenticated;) and create it with security_invoker = true, so the underlying table's RLS still applies. Our guide to views that bypass RLS explains why that matters.
Server code using the secret or service_role key
The service_role key skips RLS, but it still needs a grant. Edge Functions, cron jobs and webhook handlers that write to a new table fail too, not just the browser. If the 42501 hint names service_role, add grant select, insert, update, delete on public.your_table to service_role;.
Preview branches and new projects
Anything that builds a fresh database from your migrations (a preview branch, a staging project, a new project per customer) gets the new defaults. If a migration has no grant lines, the table is unreachable there even when production works.
Works locally, broken on Supabase
The Supabase CLI has a [api] auto_expose_new_tables setting in supabase/config.toml, and its default changed more than once during 2026. Set auto_expose_new_tables = false so your local database behaves like your hosted project, then run supabase db reset and test the app.
3. Find tables with a policy but no grant
A policy only runs if the role has the grant first. This lists every policy for anon or authenticated in public where that role can't actually reach the table:
select p.tablename, r.role, p.cmd
from pg_policies p
cross join lateral unnest(p.roles) as r(role)
where p.schemaname = 'public'
and r.role in ('anon', 'authenticated')
and not has_table_privilege(
r.role::text,
format('%I.%I', p.schemaname, p.tablename),
case p.cmd when 'ALL' then 'SELECT' else p.cmd end)
order by 1, 2, 3;
On a healthy project it returns nothing. Each row is a table your app will get 42501 from. (Policies written for the public role aren't listed, so check those by hand.)
4. Fix it the safe way
Put the grant, RLS and the policy in the same migration that creates the table, and only grant what the app uses:
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;
alter table public.your_table enable row level security;
create policy "Owners read their rows" on public.your_table
for select to authenticated using ((select auth.uid()) = user_id);
Leave anon out unless signed-out visitors should read the table. The full walkthrough, including the sequence error on inserts, is in our 42501 permission denied guide.
What not to do
- Don't run
grant all on all tables in schema public to anon, authenticated. It opens every table, including any with RLS turned off, to anyone with your public key. - Don't add back
alter default privileges ... grant ... on tables to anon. That's the rollback for the whole change, and every future table would be open again. Search your migrations foralter default privilegesand read each hit. - Don't turn RLS off to "test". The grant is what's missing, not the policy.
If an AI tool writes your migrations, add this to its instructions: "Every new table in public gets explicit grants per role, RLS enabled and policies in the same migration. Never grant on all tables in schema public."
Quick checklist
- Checked whether the project has switched (query 1)
- No migration drops and recreates a table without grants
- New views granted and created with
security_invoker - Server code has a
service_rolegrant on new tables - Local
auto_expose_new_tables = falseso local matches production - Query 3 returns no rows
Stuck on this? Get it fixed for €49.
Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.
Get it fixed for €49Still stuck?
Mendlark fixes this kind of problem for a fixed €49 (launch price, normally €79). We agree the problem first, test the fix and send it as a pull request, so nothing changes in your app until you merge it. If we can't fix it, you don't pay. Get the €49 fix, or start with a free scan.
Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.