Fine-tuning what a user can open
Override a role's default sections per user — including the trap that it replaces, not adds.
Roles cover most cases. When they do not — a Sales Staff member who also books stock in, an operator who must not see costs — you can set a per-user list of sections that overrides the role.
Setting an override
Edit the user in Users. Below the role you get every section as a checkbox, grouped the same way as the sidebar. The boxes start ticked to match the role, and from there every one is yours to change.
You can both add sections the role would not include and remove ones it normally would. Dashboard is always granted and shown locked — it is where people land.
The override replaces the role's list — it does not add to it
This is the one thing to get right. Once you tick anything, the boxes are the complete list of what that user may open, not extras on top of the role. Tick only “Inventory” for a Sales user and you have removed Customers and Quotations. Leave the role's boxes ticked and add to them.
Going back to the role defaults
Clear the override — leave no explicit selection — and the user falls back to whatever their role grants. That also means they follow any future change to the role's defaults, which a fixed list would not.
Admins are exempt
Administrators always have every section, and the editor says so instead of showing checkboxes. If you need to restrict someone, give them a different role first.
Access is not the same as your plan
| Plan | Access | |
|---|---|---|
| Applies to | The whole business | One user |
| Decides | Which modules exist at all | Which of those a person may open |
| Changed in | Subscription | Users |
| Looks like | A padlock and an Upgrade chip | The section simply is not there |
Granting someone Quotations on the Free plan gives them a padlocked entry, not the feature. The plan has to allow it first — see Plans and limits.
Note
Help is deliberately outside both systems. Every guide is readable by every user regardless of role or plan — and, since the documentation is public, without signing in at all.
Open Users
Related guides