Menu

Supabase's 30 Oct 2026 change: 'permission denied for table' and the one-line fix that leaks your data
📰

Supabase's 30 Oct 2026 change: 'permission denied for table' and the one-line fix that leaks your data

DEV Community: postgres·Karthikein M R·4 days ago
#lO3aSUdI
#devtopostgresql#devto#dev#grant#table
Reading 0:00
15s threshold

On 30 October 2026 , Supabase stops giving new tables in the public schema automatic access through the Data API (the REST and GraphQL API that supabase-js uses). It applies to all existing projects. New projects have had this default since 30 May. Source: Supabase changelog and GitHub discussion #45329 .

Tables you already have keep working. RLS works the same way. Direct Postgres connections are not affected.

What changes: the next time you (or your AI agent) create a table, the app cannot read it until you add a GRANT .

What you will see

I ran this on a local Supabase (CLI 2.121.0). I turned off the default grants the way the changelog describes, created a new table without RLS, and called it with the anon key:

{ "code" : "42501" , "hint" : "Grant the required privileges to the current role with: GRANT SELECT ON public.oct30_notes TO anon;" , "message" : "permission denied for table oct30_notes" }

Enter fullscreen mode

Exit fullscreen mode

The error is clear, and it suggests a fix.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.