From Oct 30, 2026, Supabase will apply a change to existing projects: new tables in public won't be visible to the Data API until you grant access. Supabase's changelog puts it like this:

"Once the change is rolled out to your project, new tables you create in public schema require an explicit opt-in (via a Postgres grant ) before the Data API can see them. Existing tables are not affected in your project, they keep their current grants and stay reachable."

Once the change reaches your project, the first new table you add will likely fail with 42501 permission denied for table . And the quickest-looking fix, often the one an AI assistant suggests, is this:

-- Don't run this grant all on all tables in schema public to anon ;

Enter fullscreen mode

Exit fullscreen mode

If you want the full walkthrough of what 42501 means, we covered it in the first article .…