Self-initiated demo by Flow Lab · checked on its own test Supabase project (schema copied from its own Lovable demo app) · no client data · the flagged table was created for the test and deleted afterwards
Sample report · Supabase October 30 readiness

Will your app still reach its new tables after October 30?

From October 30, 2026, Supabase no longer opens new tables in the public schema to the Data API automatically. The change applies to every existing project. Tables you already have keep working. A table added after that date without an explicit GRANT answers every app request with permission denied (error 42501), however good its row level security is. Source: Supabase changelog.

16tables in public checked
15ready: RLS on, a policy, API roles have access
1new table needs an explicit GRANT (42501), SQL fix included
0tables open without RLS

What was checked

The owner runs one read-only query in the project’s SQL Editor with their own login, so passwords and keys stay in the account. For every table in public: is row level security on, how many policies it has, and what the API roles anon, authenticated and service_role are allowed to do. If the app keeps its migrations in a repository, the same check runs on the migration files: which tables are created without an explicit GRANT or without RLS.

Summary

#What the check foundRiskResult
1t_after_1030: created the way every new table will be created after October 30, with no grants for the API roles. Any screen reading it would get “permission denied” until the grants are added.Needs GRANT for new featuresFix SQL generated
215 existing tables (bookings, clients, dogs, leads, outbox, services, settings…): RLS on, one policy each, API roles have accessOKReady as is
3Tables open without RLSNone foundNothing to fix

Finding

Needs GRANT for new features

A new table that needs API grants

What
The table exists, but anon, authenticated and service_role have no privileges on it. The app’s request receives error 42501 before row level security is even consulted.
Why now
In projects created before May 30, 2026, Supabase adds these grants for you until October 30. After that date, every table created by a migration, by an AI builder or in the dashboard needs an explicit GRANT, the same as this one.
Fix
Explicit grants in the same migration that creates the table. The check generates them, and they are applied only after the table’s RLS policies are reviewed:
grant select, insert, update, delete on public.t_after_1030 to authenticated;
grant select, insert, update, delete on public.t_after_1030 to service_role;
-- anon: only if guests are meant to see it and an RLS policy allows them

Retest: the same query then shows the table as ready.

The check, as it ran

tbl            rls    policies  anon  authenticated  service_role  risk
t_after_1030   false  0         none  none           none          needs GRANT; API requests get 42501
automation_runs true  1         ✓     ✓              ✓             ready; write GRANT for new tables
bookings       true   1         ✓     ✓              ✓             ready; write GRANT for new tables
clients        true   1         ✓     ✓              ✓             ready; write GRANT for new tables
…               15 tables ready in total

Run by Flow Lab on September 30, 2026, in the SQL Editor of its own test project. The query only reads the system catalog; it changes nothing.

What you get for your app

Flow Lab · trading.flowlab@gmail.com · The Supabase change applies to new tables only: existing tables keep their access before and after October 30.