System Admin Tool

A standalone operations console where platform operators register new hospitals on the platform, manage each hospital's admin accounts and permissions, and review attendance records.

Who uses it

• Operators who run the Hereby platform itself (the platform operations team, not hospital end users)

What you can do

• Provision a new hospital (organization) in one step, with its details, initial admin account, and default roles and permissions all set up together.
• List and search every registered hospital.
• Review and edit per-hospital settings (name, legal name, type, size, timezone, fiscal year).
• Create, edit, reset the password for, and delete a hospital's admin accounts. New admin accounts are forced to change their password on first login.
• Manage roles and permissions for each hospital.
• Review attendance records across all hospitals, filtered by organization, date range, employee number, and status.
• Create non-Root local access accounts for external collaborators who cannot use the approved Google Workspace. Each account receives one scoped role assignment with a required expiry, must replace its temporary password on first login, and must enroll TOTP before a session is issued.
• Keep identity administration separate from authorization administration: admin_user:manage.global controls account lifecycle, while sysadmin_access:manage.global controls roles and assignments. Creating or approving an account with an assignment requires both permissions.

Key areas

• Organizations: full hospital list with detail views, settings editing, and admin account / role / permission management.
• Provisioning: stand up a new hospital end to end — organization creation through initial admin account and default permissions — in one action.
• Attendance: review and filter attendance records from every hospital in one place.
• System Admin access: manage Google SSO applicants and local email accounts without granting Root or SUPER_ADMIN access.

For technical makeup (ports, routes, auth, security settings) see the Development Guide.