Managing people
- Where
- Setups → Administration → Users
- Plan
- Growth and above
- Permission
- Administration → User
What a role is and how to build one is covered in Roles and permissions. This page is the Users screen itself.
Step one: create the account
Section titled “Step one: create the account”- Go to Setups → Administration → Users and click New user.
- Fill in the Username and Email — both required.
- Add First name, Last name and Phone number if you want them.
- Type a Password, at least 8 characters. You are setting their password, and they can sign in with it straight away.
- Leave Active on Yes.
- Under Roles, tick the roles they should have.
- Save.
What the columns mean
Section titled “What the columns mean”Verified shows two dots, for email and phone. They turn colour when the person has confirmed that address themselves — you cannot mark someone verified.
Access is the one most likely to mislead:
| Badge | What it really means |
|---|---|
| Reset pending | Require password change is switched on — but nothing ever acts on it. The person is never asked to change anything and the badge never clears. |
| Lockout on | Failed-password lockout applies to this account. This is the normal, safer state. |
| OK | Lockout has been switched off for this account. |
So the green OK badge actually marks your less protected accounts, and no badge ever tells you someone is locked out right now.
The Status filter above the table does nothing — picking Active or Inactive leaves the list unchanged.
Step two: give them access to a branch
Section titled “Step two: give them access to a branch”- On the user’s row, open the ⋮ menu and click Manage access.
- Click Assign location.
- Choose a specific location, or the whole company — which shows as Whole company.
- Optionally set a date window, otherwise it reads Always.
- Save.
One person can hold several grants across several companies and branches. What they picked in the top-bar switcher is drawn from exactly this list.
You can also use Edit denials on a grant to take a permission away from someone just at that branch.
Giving or denying one person a single permission
Section titled “Giving or denying one person a single permission”Roles handle most of it, but you can adjust one person directly.
- On their row, click Manage permissions. The dialog is headed Permissions — name.
- Find the permission, using Filter permissions if the list is long.
- Then either:
- tick it to grant it to this person on top of their roles — it shows as Direct; or
- on something they get from a role — marked From role with a padlock — click the red ×, Deny for this user.
- Click Save permissions.
A denial always wins, even over a role that grants it. To undo one, click the ↻ button, Remove the denial.
You can only deny something a role already grants. There is no way to block a permission in advance.
Changing a password for someone
Section titled “Changing a password for someone”Edit the user and type a new Password — leaving it blank keeps the current one.
When someone leaves
Section titled “When someone leaves”Deactivate them. Use the Deactivate row action, or set Active to No. They can no longer sign in, their history stays intact, and you can bring them back with Activate at any time.
Plan limits
Section titled “Plan limits”| Plan | Users |
|---|---|
| Essential | 2 |
| Standard | 8 |
| Growth | 12 |
| Professional | 20 |
| Enterprise | 45 |
Over the limit, saving fails with “Your plan allows N users and you have M. Upgrade or remove one to add more.”