Checking access …
Your session and narrowly scoped management permission are being checked.
Protected workspace
Manage members.
Invite people, manage accounts and trace every decision.
Checking permission
protected
Member management
The workspace.
Email addresses and management actions are loaded only after sign-in and a server-side permission check.
Sign-in required
Sign in securely first.
Open your account and sign in. You can then return here; your session remains active on this website.
Go to your accountNot authorised
Member management isn't available for this account.
Sign-in works, but the permission manage_members:GemDen is missing. That's why no members or email addresses are shown.
Step 1
Invite a member
Submitting immediately sends a real invitation email through Supabase. The new profile remains private and does not yet receive any additional permissions.
Edit accounts
Members, access and permissions
You can manage names, sign-in access and status here. Every change needs a reason; the fixed ID remains separate and unchangeable.
Traceable history
Who decided what?
Invitations, name changes, sign-in links, account status, IDs and neighbourhood permissions are logged without passwords or email contents.
How to use it
How to manage the entire account lifecycle.
Account access, member identity and additional permissions remain separate decisions. This allows each step to be checked individually and reversed if necessary.
-
1
Invite
Enter a name and email address and send the invitation. Supabase creates the account with a private profile draft and sends the link.
-
2
Confirm member ID
For the new account, check the suggested
MEM-*-ID and assign it permanently. This ID remains stable. -
3
Accept invitation
The member opens the email link, arrives in their personal account and sets their own password with at least twelve characters.
-
4
Manage the account later
The display name can be corrected with a reason, and a new one-time link can be sent if the previous link has expired. Disabling an account blocks sign-in and database permissions; reactivating it restores both.
-
5
Optional neighbourhood permission
Only if separately authorised: select a neighbourhood, document the reason and grant the limited permission. It can later be revoked with a new reason.
-
6
Review history
At the bottom of the workspace, you'll see the time, the management account that acted, the member concerned, the decision and the reason.
If an invitation link expires: The member opens their account, enters the same email address and requests a new one-time link there. There's no need to create a second account.