Supabase RLS Review Prompt Pack
Eight prompts and a test matrix for proving that row level security protects a Supabase app before launch.
Replace the assumption that RLS is on with executed evidence of what each role can read and change.
Prompt pack · Infrastructure · PDF, 17 pages · Free · Updated 2026-11-22
What you will accomplish
What is inside
Written for: Founders launching on Supabase; Teams shipping AI-built apps; Engineers reviewing database access.
Preview
Policy-by-policy review
Read each policy as a rule about a request, and name the request it wrongly allows.
Review every row level security policy on [TABLES IN SCOPE]. Intended access model: [OWNERSHIP MODEL]. Read each CREATE POLICY, ALTER POLICY and DROP POLICY statement in [MIGRATIONS PATH] in file order and use the final definition. For each policy state the command, the roles in its TO clause, whether it is permissive or restrictive, the USING expression, and the WITH CHECK expression.
Tenant isolation test
Act as one tenant's user and try every route into another tenant's rows.
Prove that one tenant cannot read or change another tenant's data. Use only [NON-PROD DATABASE] with seeded data. If seeds are missing, stop and list what is needed. Tenancy is carried by [TENANT COLUMN]. [TEST USER A] belongs to tenant A and [TEST USER B] belongs to tenant B. Run every attempt inside a transaction that is rolled back.