Check yours in 4 steps

Check every table in your Supabase project with the free tool. It reads settings, never your rows.

·

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

Transcript

Don’t guess if your Supabase tables are open. Check in four steps. One: open the free tool, click Check my project, then Copy the query. It reads settings, never your rows.

Two: in Supabase, open the SQL Editor. Paste. Run. Three: copy the one value it returns, all of it, and paste it back. What you paste stays in your browser, and it’s never sent.

Four: read the board. One row per table. Out: signed out, anyone with your public key. In: signed in. Profiles has row-level security, the rules for who reads what, turned off.

Red All rows: anyone can read, change or delete every row, signed in or not. Notes has RLS on, yet anyone can read every note. On purpose? Only you know. 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 3 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.
  • 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.