A few things that are easy to miss with this change, from replaying migration histories without automatic grants: 1. If your first migration came from `supabase db pull`, it probably contains `alter default privileges ... grant all on tables to anon, authenticated, service_role`. Replaying it (`supabase db reset`, preview branches) turns automatic grants back on, so a missing grant only shows up in production. Put the opt-in revoke in a migration after that baseline. 2. The published revoke covers select, insert, update, delete (and sequence usage, select). Truncate, references and trigger are still granted by default. 3. `service_role` bypasses RLS, not grants: edge functions hit 42501 too. 4. A policy `to authenticated` on a table `authenticated` has no grant on never applies. 5. A `serial` key needs `grant usage on sequence` for client inserts. Identity and uuid keys don't. In 98 of 100 public histories I replayed, at least one table ended up unreachable for some role. I wrote a small open source linter for these checks (reads migration files only, never connects): https://github.com/guptaaman678/supabase-grants-lint Not affiliated with Supabase; false-positive reports welcome.