Adding Users
A person in MahirRMS is one record: their login, their role, their position on the floor, and their employment details live in a single add/edit form. There is no separate "create the employee, then create the user" dance — one form, one person.
What the form covers
- Identity — name, contact details, photograph where receipts or HR need one.
- Login credentials — username and password. For quick POS actions, a user can also carry a PIN or an RFID card where the branch has enabled those credential types.
- Role — which permission bundle they get (see Roles & Permissions).
- Position — what they are on the floor: cashier, manager, rider and so on. Position matters operationally: registers are created for cashiers, riders appear in delivery assignment, and the authorization rules treat cashiers specially.
- Branch — where they work. Multi-branch businesses assign people to their location.
- Employment details — the HR-side facts (joining date, salary information where used) in the same form.
Passwords and credential hygiene
Users change their own passwords; administrators can reset them. PIN and RFID credentials are for speed at the POS — treat a PIN like a password (it authorizes discounts and register actions where enabled), and retire an RFID card the day it goes missing.
Disabling a user
When someone leaves, disable the user rather than deleting history. A disabled user cannot sign in, cannot be selected as an authorizer, and is rejected server-side even if a stale screen still lists them. Their name stays on every historical order, register and signature — history is never rewritten.
Leavers checklist: disable the login, remove them from branch authorizer lists, close out their register if one is open, and settle their staff clearing balance (visible in one line if the staff sub-ledger is on).