Account users and roles
Add colleagues on the account, give them a role that matches their job, and never share a password. Platform internals stay out of this guide.
An account user is a colleague who signs into the dashboard. A role sets what they see and what they can change: requests, properties, reports. You add colleagues on the users list and assign a role from the account’s roles.
On All branches, the users list shows every assigned branch on the row (for example Jeddah · Riyadh) and a branch filter. Staff assigned to only one branch do not see that column — the header already scopes the list.
Add a colleague carefully
- Add the name and the email or mobile they will use to sign in.
- They are assigned to the branch you are viewing in the header. Switch first if they should start in another branch.
- Choose an existing role that matches daily work — not a wider role than they need.
- Ask them to complete their profile and verification if those steps appear after first sign-in.
- If they forget the password, use the reset action your role shows. Do not send a password in a group chat.
Do not give the account-supervisor role to someone who only reviews requests. This public guide does not document platform-admin permissions or identity switching.
Tip: Recheck the role a week after the colleague joins. If they open screens outside their job, narrow the role instead of inventing verbal exceptions.
Service providers and customers are different records. Do not create a dashboard user for every resident who scans a code.
What to read next
- Service providers — a field record is not a dashboard user.
- Customers — do not create a dashboard user for every resident who scans a code.
- Branches — switch the header branch before you add a colleague who should start elsewhere.
- Account settings — what the account supervisor sets on forms and services.