Fix it without breaking your app

Turn row-level security on with the right rules in place, so your app’s lists don’t come back empty.

·

The player loads from YouTube (youtube-nocookie.com) when you press play.

Transcript

Will fixing Supabase RLS break your app? Not if you add rules first. RLS decides who reads what. Turn it on with no rules, and your lists come back empty. Open the first finding. It explains the problem in plain words, with a fix.

This fix adds rules too: users get only their own profile. Notes still need work. To write every rule at once, open Generate policies. It doesn’t read your project, so start from Personal app and rename tables to match.

Each click sets who can do what, and the card shows you the Postgres policy. It removes your old rules, even the one that let anyone read everything. If it’s meant for everyone, set Anyone to Yes.

Copy the SQL and run it in the SQL Editor, on a test project first. Run the check again. Paste the new value. Nothing serious found. Signed out, you see nothing. Signed in, you see only your own rows.

Free, no sign-up. Link in the description.

Sources

Where the facts in this video come from. Everything shown on screen is a test project with made-up data.

Check your own project for free.

Generate row-level security policies and check a schema for tables left open.

Open the Supabase RLS Generator

More videos

  • Is My App Open? · Part 1 One key, every row Why the key in your app’s page can read every row of a Supabase table when row-level security is off.
  • Is My App Open? · Part 2 Check yours in 4 steps Check every table in your Supabase project with the free tool. It reads settings, never your rows.
  • Is My App Open? · Full demo Check and fix Supabase RLS, step by step The whole check on a test project: copy the catalog query, read who can reach each table, apply the fixes, generate policies, test as each user and check again.