---
title: "Comment by Last Mile on \"Fixing \"new row violates row-level security policy\" in Supabase\" | Hashnode"
description: "Nice walkthrough. One thing worth adding to the missing-grant case: from Oct 30 2026, new tables in the public schema on existing projects get no default grants"
url: "https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d/comment/6ad9308ed26e237a1c7b2b99"
---

[Discussion](https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d)

Comment [Fixing "new row violates row-level security policy" in Supabase](https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d)

[Last Mile](https://hashnode.com/@lastmilekit)

[Oct 21](https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d/comment/6ad9308ed26e237a1c7b2b99)

Nice walkthrough. One thing worth adding to the missing-grant case: from Oct 30 2026, new tables in the public schema on existing projects get no default grants for anon/authenticated, so a brand-new table can return 42501 before any policy is even evaluated. The safe fix is explicit per-role GRANTs (e.g. grant select, insert on public.projects to authenticated) plus enable row level security and the policies in the same migration, rather than disabling RLS or a bulk "grant all on all tables".
