Supabase "permission denied for table"? New tables need a GRANT now
Ship ItChecked against the official source
Source checked 4 Oct 2026 · Published 21 Oct 2026 · Last reviewed 21 Oct 2026 · By Ctrl+Z Therapy (how we test)
The short answer
Supabase made a breaking change: new tables in the public schema are no longer exposed to the Data API automatically. That's the API your app's Supabase client talks to, so a new table can give "permission denied for table". New projects have had this default since May 30, 2026, and on October 30, 2026 it is applied to all existing projects. Existing tables keep their current grants and stay reachable, and RLS behavior is unchanged.
What to do
- Open the SQL Editor in Supabase and grant access to each new table (GRANT).
- Enable RLS on that table and add policies. Do all three: grant, RLS, policies.
- If an AI tool creates your tables, Supabase says to update its system prompt.
- Ask your AI tool: "Whenever you create a Supabase table, also add the GRANT statements, enable RLS and add policies."
Good to know
- We checked this for Supabase projects. We haven't checked how Lovable Cloud handles it.
Source
- Supabase: Breaking change, tables not exposed to the Data API automatically
- Supabase: Securing your API
Checked on 4 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.