SYSTEM ADMIN
/manage/accounts

Staff accounts & access

Everyone inside the organisation, and every partner, who can reach /manage/*. An account has three states and no others: created by a system admin → active → revoked. There is no "temporarily hidden" state, no self sign-up, and no shared account for a team.

Granting and revoking access takes two people

This is the strongest power in the system: whoever holds it could grant themselves everything else. So every change to a role — adding one, removing one, or revoking access altogether — goes through a request, requires a written reason, and only takes effect once a different active System admin (R08) account approves it.

The requester and approver must be two different R08 accounts. Holding a clinical, content, sponsorship or analyst role does not confer either power. Someone who holds several roles still cannot approve their own request: the constraint sits in the data layer, not in a hidden button.

All · 11 Active · 8 Two-factor not set up · 1 Revoked · 2
Account Role Two-factor Last sign-in Status Action
Marcus Hale
marcus.hale@tibbi.org.au
System admin R08 On 27/07/2026 08:12 Active This is you — you cannot change your own access
Aisha Nguyen
aisha.nguyen@tibbi.org.au
System admin R08 On 27/07/2026 07:58 Active
Jonah Reed
jonah.reed@tibbi.org.au
System admin R08 On 26/07/2026 18:22 Active
Sam Okafor
sam.okafor@tibbi.org.au
Content admin On 27/07/2026 07:45 Active
Dr Alice Brennan
alice.brennan@tibbi.org.au
Clinical reviewer On 26/07/2026 16:30 Active
Tom Whitfield
tom.whitfield@tibbi.org.au
Sponsorship manager On 25/07/2026 11:02 Active
Priya Raman
priya.raman@tibbi.org.au
Impact analyst On 27/07/2026 06:40 Active
Elena Marsh · Riverside Grocers
elena.marsh@riversidegrocers.example
Sponsor external On 24/07/2026 09:15 Active
Nina Ward
nina.ward@tibbi.org.au
Content admin Not set up Never signed in Awaiting activation Cannot reach /manage/* until two-factor is set up
Grace Tan
grace.tan@tibbi.org.au
— (content admin revoked) 02/06/2026 14:20 Revoked Revoked 03/06 · requested by Marcus Hale (R08), approved by Aisha Nguyen (R08) · reason: contract ended
Northside Bakery
accounts@northsidebakery.example
— (sponsor revoked) 18/05/2026 10:07 Revoked Revoked 19/05 · requested by Jonah Reed (R08), approved by Marcus Hale (R08) · reason: campaign finished

Player accounts are not listed here. They live under players and cooldown, and only ever appear as an anonymous code.

Requests waiting on a second person

2
#AC-0117 · Add the impact analyst role for Sam Okafor Raised by Marcus Hale (R08) on 27/07 · reason: Sam is covering pilot reporting while Priya is on leave, limited to 31/08 · waiting on Aisha Nguyen (R08)
Awaiting approval
#AC-0116 · Revoke all access for Nina Ward Raised by Aisha Nguyen (R08) on 26/07 · reason: two-factor still not set up after 14 days, policy is to revoke and re-issue · waiting on you

You can approve #AC-0116 because Aisha Nguyen, another R08, raised it. You cannot approve #AC-0117 because you raised it yourself — there is no approve button on that row, and the endpoint refuses it in the data layer if it is called directly.

Changes to access

cannot be deleted
WhenChangeRequested byApproved by
19/05 10:41Sponsor access revoked · Northside BakeryJonah Reed · R08Marcus Hale · R08
03/06 09:12Content admin revoked · Grace TanMarcus Hale · R08Aisha Nguyen · R08
14/07 15:26Content admin account created · Nina WardAisha Nguyen · R08Marcus Hale · R08
20/07 08:03Two-factor device re-issued · Priya RamanJonah Reed · R08Aisha Nguyen · R08
26/07 17:55Revocation requested · Nina WardAisha Nguyen · R08waiting

This record survives account deletion: it holds who gave access to whom, not personal data about the people who use the app. It covers changes to access only — every read of a player's record is kept separately in the sensitive data access log, under the same rule that no row can be edited or removed.

Open the access log

Not available here: viewing or resetting someone else's password · switching off two-factor on an active account · signing in as another person, which would destroy every audit trail · creating player accounts from the admin area · and, above all, no way to raise your own access.