Users, Sign-in & Permissions

User accounts, sign-in, roles, permission groups and who can see what.

How-to guides

Create a user
Add a portal user to your organisation with a username, a confirmed password, a department and a role.
Change a user's role
Give a user a different role in your organisation; the new access applies on their next click and the change is recorded in the audit log.
Delete a user
Remove a user's access; the username is released so the same phone number or name can be given to a new account.
Change a password
Change your own password, or set a new one for a user you manage, without being signed out.
Give a driver a Driver App login
When adding or editing a driver, link an existing user, create a login in the same form, or record the driver with no login at all.
Prepare a driver or staff import file
The identity rules for driver and staff rows in a bulk import — phone or email required, how usernames are made, and which rows are rejected as duplicates.
Sign in to the portal and the Driver App
Sign in with your username (drivers use their phone number), choose the language before signing in, and what happens when your session expires.
Reset a forgotten password
Request a reset by username; the link goes only to an email address that belongs to you alone, otherwise you are asked to call the support hotline.
Change your profile picture
Upload and crop your profile picture; without one the platform shows your initial on a coloured circle.

Roles and permission groups
The nine portal roles (Platform Operator, Tenant and Merchant Owner, Admin, Supervisor, Accountant), what each is for, and why drivers sign in without a role.
What each role can do
A role × feature table of what each portal role can view, create, change and delete, including the catalog, price and voucher read access tenants hold.
Which records each user can see
How the platform limits every list, page and API answer to the user's own organisation, or for Merchant Supervisors to their assigned stores — and what happens when someone asks for a record outside it.
User accounts
The user record — username as the only sign-in key, email and phone as contact data, organisation and department, role, avatar, and what deleting a user does.
Audit log
What the platform records about every change — who, when, what changed — including role changes, bulk imports and settlement steps, and who can read the history.