Login isn't access control: the second-account test

A sign-in screen answers "who are you?". It doesn't answer "what are you allowed to see?". Here's a public case that shows the gap, and a test you can run yourself in 10 minutes.

The public case: an app with sign-in that still let outsiders in

On 10 November 2026 the security firm Claroc published research on apps built with Grok Build. Of 37,571 apps still online, Claroc reports that 35,578 opened with no sign-in at all (The Hacker News, Unite.AI). The vendor disputes some of the default-setting claims.

The useful part is a smaller detail. Claroc built its own test app, a customer list for a small sales team, and the AI added Google sign-in. But the generated code added whoever signed in to the team before checking whether they were invited. An uninvited Google account could view every customer, change one record and delete another. This was Claroc's own test app, not a real user's.

So adding "a real login" isn't the fix. The question is whether the app checks what each signed-in user is allowed to see and change.

The 10-minute second-account test

Use a test or staging copy with throwaway data. You need two accounts that are not invited to each other's data.

1. Sign in as user A. Create a record with a marker, e.g. "ZEBRA-A-123".
   Copy its URL or ID.
2. In a private window, sign up as user B (a brand-new account, no invite).
3. As B, open A's record URL directly, and try the list/search page.
4. As B, try to edit and delete A's record (change the ID in the URL
   or in the request in DevTools → Network).
5. In B's window: DevTools → Network → reload → search "ZEBRA-A".
   If it shows up in any response, A's data left the server.

Pass: B sees nothing of A's, and edits and deletes fail. Fail: any of A's data loads, or any change goes through.

Where it usually breaks

"anyone signed in" checks ........ auth.uid() is not null / role = authenticated
auto-join on sign-in ............. new users added to a team or org by default
UI-only hiding ................... the page fetches all rows, then filters on screen
IDs in URLs ...................... /customers/42 loads for any signed-in user
update without "with check" ...... a user can reassign rows to themselves

On Supabase the fix is usually row-level security scoped to the owner or the team membership, e.g. using (auth.uid() = user_id), with a matching with check. Membership has to come from an invite the app checks, not from "this person signed in". The step-by-step Supabase version for every verb is in "RLS enabled" isn't a green light.

Don't want to write it yourself?

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: test your Supabase app as a second user · the 10-minute Supabase self-check · is my anon key a problem?