Supabase Grants Change: What Breaks After October 30, 2026
By Matt Cullerton, founder of Mavric and Apso
Supabase is changing Postgres default privileges so that new tables in the public schema are no longer reachable through its Data API (the REST and GraphQL layer supabase-js calls) until you add explicit grant statements. Row Level Security (RLS) does not change, existing tables keep working, and new projects have used this behavior since May 30, 2026. October 30, 2026 is the date it reaches existing projects.
A TikTok from @ducktate.com warns that the update "could break your app" and that after October 30 new tables will be private so "nobody can see it." The warning is useful. The mechanism, the dates and the scope need corrections.
What is changing in Supabase?
Supabase's April 28, 2026 changelog entry describes the old default: "select, insert, update, and delete are granted to every table in the public schema to the anon, authenticated and service_role roles." The new default removes that automatic grant. The changelog lists the statements Supabase runs:
alter default privileges for role postgres in schema public
revoke select, insert, update, delete on tables from anon, authenticated, service_role;
alter default privileges for role postgres in schema public
revoke usage, select on sequences from anon, authenticated, service_role;
After the change, each new table needs an explicit grant before the Data API can reach it.
Does this change Row Level Security?
It does not. The video says "if I didn't have any row-level security or the correct permissions set," which treats two layers as one. The changelog separates them: "RLS behavior remains unchanged. Grants are a separate layer: they control whether a role can access a table at all, while RLS controls which rows that role can see." Its before-and-after table marks both enable row level security and create policy as "Remains the same."
When does the Supabase change take effect?
The rollout has three main dates:
- April 28, 2026: the changelog and an opt-in toggle at project creation ("Automatically expose new tables").
- May 30, 2026: "the new behavior becomes the default for all new projects," rolled out over a few weeks.
- October 30, 2026: "the new behavior is enforced on all existing projects."
Anyone who created a project in the five months before the video posted is already on the new behavior. Supabase maintainer @lukas-bernert summarized the scope in the GitHub discussion on May 29, 2026: "You do not have to do anything for existing tables in existing projects. However, if you do create NEW tables in public in new or existing projects, after October 30th, you need to add explicit GRANTs."
What breaks, and what keeps working?
Only the Data API is affected. The changelog says the change "applies to projects that use the Data API, Supabase's auto-generated REST and GraphQL layer." It also says: "If your app reads and writes Postgres over a direct connection (via psql, ORM or an app server with a connection string), this change will not affect you."
Only the public schema is affected. The FAQ says "Tables in storage, auth, realtime, and any custom schemas you expose via the Data API keep their current grants and their current defaults."
Existing tables keep working. Supabase says they "keep their current grants and stay reachable." Maintainer @steve-chavez confirmed on July 20, 2026 that existing tables are "not automatically affected because they already have the required grants."
New tables break. Supabase says "a project with no flagged tables today still breaks the first time someone adds a new one."
The video's "not even authenticated users, anybody" holds up, since the revoke covers service_role too, so a secret-key call through PostgREST fails the same way an anonymous one does.
What error will I see?
The changelog quotes the PostgREST response: "code": "42501", "message": "permission denied for table your_table", with the hint "Grant the required privileges to the current role with: GRANT SELECT ON public.your_table TO anon;". Supabase says it wrote the hint so "an agent can self-correct when a grant is missing instead of producing a broken request."
Were Supabase tables open to anyone before this?
That depends on how the table was created. The video says that today, a table with no security set means "anyone on the internet could read and write to that table." Supabase's Securing your API guide says "Tables created through the Supabase Dashboard have RLS enabled by default." A table with RLS on and no policies returns nothing to anon or authenticated.
Tables created in the SQL Editor, through migrations, by a CLI script or by an AI coding agent do not get RLS automatically. Under the old default grants, those tables were exposed. Supabase's guide warns: "Tables and views exposed through the Data API without RLS can be accessed by any role with matching grants." Supabase's API keys page says of the publishable key, which ships in client code: "Anyone can read it, so it only reaches what Row Level Security allows."
Supabase gives this gap as its reason for the change: "Today, agents, CLI scripts, and AI platforms create tables too, and many of those operations do not have a human reviewing the diff."
Will AI coding tools know about the change?
The video says "your AI is not going to know that." That cannot be checked across every tool. Supabase did publish guidance for agents. Its Agent Skills post from April 9, 2026 supports "Claude Code, Codex, GitHub Copilot, Cursor, or any of the agents that support Agent Skills Open Standard," installed with npx skills add supabase/agent-skills. The changelog tells readers to "update its system prompt or adopt the Supabase agent skill, which includes the grants step."
A note on the Ducktate example
The creator uses his app, Ducktate, as the example and says it stores "all of the encrypted notes for all of my users." Ducktate's pricing page lists "Encryption Mode" in the $9.99 per month Pro tier with cloud notes. The Free tier keeps notes on the user's Mac.
Bottom line
If you add tables to public and read them through supabase-js, add explicit grant statements for each new table. RLS policies still decide which rows each role sees.
Sources
- Supabase changelog, April 28, 2026: dates, revoke statements, error format, scope and FAQ.
- GitHub discussion #45329: maintainer replies on new and existing tables.
- Securing your API: RLS defaults by creation path.
- API Keys: what the publishable key can reach.
- Supabase Agent Skills post: guidance for AI coding tools.
- Ducktate: the creator's app.
- Ducktate pricing: where Encryption Mode sits.
Published October 19, 2026. Based on a TikTok by @ducktate.com. Full video notes (markdown)