"Enabled" only means the switch is on. Whether user B can read, change or delete user A's rows depends on the policies, and the dashboard won't warn you. Here's a 10-minute two-account test.
A URL scanner hits your API with the public anon key and no session. That catches tables with RLS off. It can't see a policy like using (auth.role() = 'authenticated'), which lets every signed-in user read every row. You only find that by signing in as someone else and trying.
Sign up twice in your own app (for example a@test.local and b@test.local). As user A, create one row in every table that holds user data: a profile, an order, a message, a file.
Save as rls-b-test.mjs, fill in your project URL, anon key and user B's password, then run npm i @supabase/supabase-js && node rls-b-test.mjs.
import { createClient } from "@supabase/supabase-js";
const sb = createClient("https://YOUR-PROJECT.supabase.co", "YOUR_ANON_KEY");
await sb.auth.signInWithPassword({ email: "b@test.local", password: "..." });
const { data: { user } } = await sb.auth.getUser();
const TABLES = { profiles: "id", orders: "user_id", messages: "user_id" }; // table: owner column
for (const [t, owner] of Object.entries(TABLES)) {
const read = await sb.from(t).select("*").neq(owner, user.id).limit(5);
const upd = await sb.from(t).update({ [owner]: user.id }).neq(owner, user.id).select();
const del = await sb.from(t).delete().neq(owner, user.id).select();
console.log(t, "| read others:", read.data?.length ?? read.error?.message,
"| update others:", upd.data?.length ?? upd.error?.message,
"| delete others:", del.data?.length ?? del.error?.message);
}
Every number should be 0 (or an error). Any number above 0 means user B touched rows that aren't theirs. Run it on a test project or with throwaway rows: if a policy is broken, the update and delete lines really do change user A's data.
// as user B: try to create a row that claims to belong to user A
await sb.from("orders").insert({ user_id: "USER_A_ID", total: 0 });
// then sign out and repeat the read line with no session (anon)
await sb.auth.signOut();
The insert should fail with a policy error (it needs with check (auth.uid() = user_id)). The anon read should return nothing for private tables.
using (true) ............................ everyone, even logged out
using (auth.role() = 'authenticated') .... every signed-in user
using (auth.uid() is not null) ........... every signed-in user (looks scoped, isn't)
update policy with no "with check" ....... user can reassign rows
no delete policy but grant all to anon ... check grants too
Also check what B's browser received, not just what the screen shows: in B's window open DevTools → Network, reload, and search for a marker you put in A's row. If the page asks for all rows and only hides A's on screen, the data still left the database.
The fix is almost always to scope by owner: using (auth.uid() = user_id) plus a matching with check on insert and update.
Supabase documents database tests with pgTAP, run by supabase test db, so you can keep this check as a test per table, verb and role and re-run it after every schema change. See Supabase's database testing guide.
The free Ship-Ready quick scan runs locally and flags RLS-off tables, using (true) policies and exposed keys. The Crew (59-check scan, $39) adds a two-user spec template that turns the test above into a repeatable check.
Related: the 10-minute Supabase self-check · is my anon key a problem? · Stripe webhook not verified