Supabase changes a default on 30 October: new tables will not reach your app until you grant access
From 30 October 2026 Supabase stops exposing new tables in the public schema to its Data API by default. Existing tables keep working. Here is what breaks, and how to fix it without opening your data.
How urgent
Act now
Who is affected
Apps that use the Supabase Data API (supabase-js, REST or GraphQL), above all projects built with AI tools such as Lovable that create tables without explicit grants. Apps that connect straight to Postgres are not affected
What to do
Before 30 October, check the tables your app uses, and for every new table add an explicit GRANT together with row level security and a policy. Do not fix errors by granting everything to anon
Published 27 Oct 2026 · Sources last checked 27 Oct 2026No. 15 / 87
What is changing
Supabase published a breaking change on 28 April 2026. Until now, every new table in the public schema was automatically open to its Data API: the roles anon, authenticated and service_role got select, insert, update and delete on it. That is what made a new table work the moment you created it.
Under the new default, a new table needs an explicit GRANT before the Data API can see it. According to the changelog:
- Since 30 May 2026 the new behavior is the default for new projects.
- On 30 October 2026 it is applied to all existing projects.
- Existing tables keep their current grants and stay reachable.
This applies to the Data API (REST, GraphQL and supabase-js). Apps that connect directly to Postgres with a connection string, such as an ORM or an app server, are not affected. The storage, auth and realtime schemas keep their current settings.
What you will see
If a table has no grant, the Data API returns error 42501, "permission denied for table", before row level security (RLS) is even checked. Supabase says that even a project with no flagged tables today will hit this for any new public table created after 30 October without a grant.
Who is affected
Anyone who builds an app on Supabase and creates new tables after 30 October. It matters most for projects generated with AI app builders, because the tool may create tables and policies without the grant step and nobody notices until a feature stops working. The changelog says that migrations, scripts and AI tools that create public tables without explicit grants are affected.
Why this is also a security story
The change makes new tables private by default, which is the safer starting point. The risk is in how people react to the error. The quickest way to make it disappear is to grant everything to anon and move on, and that can open a table to anyone on the internet.
Grants and RLS are two separate layers. A grant decides whether a role can reach a table at all. RLS decides which rows that role can see. If a grant is missing, Postgres rejects the query before RLS applies. You need both, set on purpose.
What to do
- Review your tables now. Supabase's Security Advisor flags affected tables and shows the fix until 30 October, and the Table Editor shows a Data API exposure badge.
- For each new table, write the three steps together. Grant, enable RLS, add a policy. The changelog example uses, in this order:
grant select, insert, update, delete on public.your_table to authenticated;thenalter table public.your_table enable row level security;thencreate policy "users can read their own rows" on public.your_table for select to authenticated using (auth.uid() = user_id); - Grant to
authenticatedfor data that belongs to signed-in users. Our advice, not Supabase's: giveanonaccess only to a table that is meant to be public, and avoid write access foranon. - Add the grant step to your migrations. If you use an AI coding tool, update its instructions so it adds grants with RLS. The changelog mentions a Supabase agent skill that includes the step.
- Check from the outside. Our open-database check on this site looks for Supabase and Firebase setups that leave data readable by anyone.
If you build with AI tools
An AI builder can generate a table that works in preview and fail in production after this change, or it can "fix" the error by granting broad access. Read what it does with permissions before you accept it.
What we could not confirm
We read the official changelog entry. We have not tested the change on a live project. The changelog does not say whether the creation-time opt-out checkbox is available on existing projects, and the label of that checkbox differs between two places in the entry. It documents the grant for tables created by the postgres role and does not say what happens for other roles. For the exact steps in your project, use the Supabase dashboard and documentation.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.