The Form Book — who's on it, what each role reaches, and how to add people.
No password? Get a code emailed to you
Just looking?
Signing in swaps the sample roster for the live accounts from the database.
PREVIEW MODE — nobody is signed in. The roster below is the sample list written into this page.
The Form Book — Members
Everything Compute · Racing
Who's on it
Everyone with access, the role each holds, and what that role reaches.
Name
Role
Email
Reaches
Login
🔓 Manage people
Only an admin account sees this. Creating or removing a login runs on the server through the manage-team function — this page never holds the master key.
Name
Email
Role
Last sign-in
Inviting sends the person an email to set their own password. No password is ever typed here or shared. Roles: admin sees everything · vet sees welfare + how it's derived · member sees the card, tips and trends.
What each role reaches
The permission model, straight from the app. This is what the sign-in actually shows each person.
Security note
No passwords appear here, and none can. Supabase stores them as one-way bcrypt hashes — confirmable when typed, never readable back, by anyone. To give access you invite the person and they set their own; you never see it.
Shared member pool. The Form Book and Ffermio Adfywiol run on the same Supabase project, so one account works across both. This dashboard signs in as an ordinary user with the publishable key and shows only what Row-Level Security returns — the service key never reaches the browser.
Login & Accounts + Role Access · reads only what Row-Level Security allows