Admin App Shell · Governance

Admin Access Control

The definitive list of who can reach the PURE admin backend. New accounts require approval by Mike and/or Shattique; when one approves, the other is automatically copied & notified.

Approvers only

Who can reach the admin app shell

This is the whole list. Everyone here reaches the admin backend; no one else does.

—

Person	Role	Email	Status	Added by

Approval policy

How a new admin account gets established

Request. A new admin account is proposed here with the person's name, email, and the role they'll wear.

Approve. The request must be approved by Mike and/or Shattique. No account is provisioned without it.

Copy & notify. The moment one approves, the other approver is automatically copied and notified that the account was established — so both always know the current roster.

Enforced everywhere. Access is checked server-side (mcp_is_admin) on every admin page and on every save — being off this list means no admin backend, regardless of role.

Request a new admin account

Approvers only. Submitting notifies the other approver for sign-off.

Full name

Email ame@acquistorealestate.com">

Role / hat

Route to

Justification

Pending requests

Awaiting approval from Mike and/or Shattique

Person	Role	Requested	Approvals	Action

Auth & security controls

Live control over the security posture: who has a second factor, which organisations require one, and which devices and sessions stay trusted. Every action is enforced server-side for super-admins — this surface only reflects what the server allows.

Second factor by person

Account	Status	Factors	Recovery	Action

Re-challenge window (hours, 0 = every sign-in)

Organisations that require MFA —

Organisation	Requirement	Action

Devices & sessions for one account

Trusted device	Kind	Last seen	Action
Look up an account to see its trusted devices.

Session started	Client	IP	Action
Look up an account to see its active sessions.

ⓘPassword re-issue is not here yet, on purpose. The account service is self-serve only — it acts on the signed-in caller and requires their current password, so it cannot reset someone else. A super-admin-gated admin path is filed as t-admin-pw-reissue; until it ships, use the person’s own reset link rather than a workaround.