Supabase · 30 October 2026

New tables start closed.

Since 30 October 2026, new tables in the public schema are no longer reachable through the app's API until a GRANT says so.

Who it hits

  • A table you add later

    You, or your AI tool, add one. Your app cannot reach it until a GRANT says so, and the answer is permission denied.

  • A project rebuilt from your code

    A new project, a branch, a staging copy, a restore: every table your files create starts without access.

  • The tables you already have

    They keep their grants and stay reachable.

The days

  1. 30 May 2026every new project
  2. 30 October 2026every existing project

Supabase’s own words

In their words.

  • “Existing tables are not affected in your project, they keep their current grants and stay reachable.”
  • “You are unaffected if you only talk to your database over a direct Postgres connection--you can stop reading.”
  • “Explicit grants make access a deliberate, code-level decision.”

Read from Supabase's own pages on 29 October 2026. /changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically

Is your app one of them?

The free check reads your migrations and says which tables have no grant. The fix is a new migration, and you apply it. Nothing changes without your yes.