NextWatch RLS Lab — v5
Isolated project: nextwatch-auth-lab. No email, AI, user creation or SMTP configuration.
Use two NEW dedicated test users only. Passwords go directly to Supabase over HTTPS. Sessions stay in memory, separately for A and B; reloading clears local credentials but does not revoke server sessions. Log out before closing.
Preparing…
1. Sign in to two test accounts
2. Prepare fixture manifest — no database writes
Generate a fresh plan only for empty accounts. Download it for review. Creation of these synthetic records requires separate approval and is not implemented on this page.
After approved fixture setup, load the exact reviewed plan:
3. Run approved RLS checks
Do not run yet. Tests require exact owner-visible synthetic baselines. They attempt cross-user reads, changes, deletion and ownership forgery, then test own writes. A failure stops the suite. Review remaining test records before cleanup.
UI checkboxes are operator safeguards, not server access controls. Supabase RLS enforces access.
Never share passwords, tokens or login links. Report outputs contain only test names and outcomes.
Back to existing Auth Lab