Administration

User Roles & Permissions

The actual system roles, what each can do, and tenant and branch scope.

Who can use: Hospital Admin

What it does

HMS enforces role-based access on the server for every request. Roles are hospital-scoped: staff act only inside their own tenant, and branch-restricted staff act only inside assigned branches.

Who can use it

Hospital Admins create and manage staff accounts. The platform Super Admin manages hospitals and subscriptions, never hospital data.

  • Super Admin — platform console only: hospitals, subscriptions, plans, quotes, audit logs, system health. Has no hospital tenant.
  • Hospital Admin — full control inside their hospital: staff, departments, doctors, branches, settings, subscription.
  • Receptionist — patient registration, appointments, queues and OPD flow.
  • Doctor — appointments and patient records, limited to patients with an appointment relationship to that doctor.
  • Billing Staff — invoices, receipts, payments and billing reports.
  • Lab Staff — lab test requests, samples and diagnostic reports.
  • Pharmacy Staff — prescriptions, dispensing, medicine stock and point of sale.

How to use it

Hospital Admins add staff from the admin console by choosing a role and, where needed, assigning branches. Staff sign in with OTP and immediately see only their permitted consoles.

Important rules

A Doctor account is matched to a doctor profile by email; without a matching profile, patient access is denied. Permissions are checked server-side — hiding a menu item never grants or removes access. Cross-hospital access is never permitted.

Common problems

Doctor sees no patients: confirm a doctor profile with the same email exists and has appointments. Missing console: the role lacks permission or the module is not active on the subscription.

Related documentation