Ffermio Adfywiol — the team, what each person can reach, and who can see whose data
No password? This is the easy way in
The code goes to that person's own inbox, so nobody has to share a password.
It only works for an address that already has an account.
Don't need live figures?
Signing in is optional. It swaps the illustrative figures for live ones from the database.
PREVIEW MODE — nobody is signed in. Figures below are illustrative.
Ffermio Adfywiol
The team
Everyone on the project, the role each holds, and what that role reaches.
Name
Role
Email
Can reach
Login
🔓 Manage people
Only an organisation account sees this panel. Changes are saved on this computer and shown on the
board straight away.
Name
Email
Role
Farm
Adding someone here gives them a place on the board — not a login. Creating an actual account
needs Supabase's admin key, which must never sit in a web page; anyone could read it and let themselves in.
So the two steps are separate on purpose: add them here, then create their account in the Supabase dashboard.
Until that exists they show as no login yet, which is the truth rather than a promise.
Changes live in this browser. “Copy this team list” gives you the lines to paste
into the page's TEAM array to make them permanent for everyone.
Who can see whose data
Read down the left for the person looking, across the top for whose farm data they are trying to reach.
This is not a wish-list — it is what the database rules produce.
✔ can see · ✘ blocked by the database · shaded = their own record
Set a password for this account
Signing in by emailed link works forever, but if you would rather type a password, set one here.
You choose it and it goes straight to the database — nobody else ever sees it, including whoever built this.
Sign in first. Only the account holder can set their own password, so these boxes stay locked
until you are signed in. Use Sign in for live figures at the top, then Email me a code — the
email contains a link; clicking it brings you back here signed in, and these boxes come alive.
Sign-in & change log
Every person added, removed or re-roled, and who did it. Append-only — the database has no
update or delete policy on this table, so a line cannot be quietly edited out.
When
Who
Did what
To whom
Detail
Security note
No passwords appear here, and none can. Supabase stores them as one-way bcrypt hashes — the
database can confirm a password when it is typed but cannot reveal it. Nobody can read them back, including
the people who built this. To give someone access you set a new password in the Supabase dashboard; you never
recover the old one.
This dashboard has no special powers. In live mode it signs in as an ordinary user with the
publishable key, exactly as the app does, and shows whatever Row-Level Security returned. Sign in as a farmer
and the team table collapses to one row — not because the page hides the others, but because the database
declines to send them. The service key, which would bypass all of it, never reaches the browser.
Not shown: other people's sign-in times. A browser session can read only its own.
Login & Accounts + Organisation Access · reads only what Row-Level Security allows