Assigning permissions correctly in practice
Roles, module rights, visibility and typical permission errors in SimpliServ explained clearly
→ Open employees · Manage roles
Permissions determine which data and actions a user may use. How roles and users are created technically is described in Users & roles. The menu item is just navigation. It is not the same as the right to open a route or save an action.
The permission principle
Many modules split actions by this pattern:
*.view– see list or detail.*.create– create a new record.*.update– change an existing record.*.delete– delete or remove a record.
Additional specialist rights control special actions, for example sending email, converting to an invoice, cash register reports or import/export.
Create and assign a role
Open the role
Open Administration → Team & security → Roles and choose an existing role or New role.
Choose rights by job
In the Permissions card the rights are grouped by module and searchable. Only grant the groups the workstation needs. Start with view and add create, edit and special actions separately.
Save the role
Save the role via the save bar. The Enabled filter shows which rights are actually active.
Assign users
Open the user, click Edit user and pick the role under Roles. The Permissions card in the profile then shows all effective rights. Afterwards test with a user of this role in a new session.
Typical combinations
Sales
A sales employee usually needs contacts, leads, proposals and orders to view and edit. Invoices and sending email should only be added if the person really takes on these tasks.
Till
For daily sales the user needs the till view and the till action. Reports, setup and fiscalisation are separate. A cashier should not automatically be allowed to edit till or organisation settings.
Warehouse
Warehouse staff need products, stock, warehouses and possibly serial numbers. Purchasing or finance rights are not automatically required.
Workshop
Technicians who should only see their own work get Tickets → View own instead of Tickets → View all. They then only see tickets assigned to them, including their orders, plus orders they created themselves. With Tickets → View own offices all tickets of their offices are added. If Multiple staff per order is on, every assigned person counts, not just the one picked first.
Administration
Administration → Settings → View allows viewing settings; Administration → Settings → Edit allows saving them. This separation matters for employees who should review configurations but not change them.
Why a user is blocked despite the menu item
- The action has an additional special right.
- The route needs a stronger permission than the list.
- The module is disabled.
- The record belongs to a context the user may not see – such as a contact group outside Restrict customer groups.
- The navigation was changed in the navigation editor, but the role wasn't.
- A session still uses old permission data.
Sign out and back in after a role change before testing. Also check a direct link and the visible action separately.
Don't hide sensitive areas only via the menu. Security comes from the server/route permission; navigation is just discoverability.
Test rights safely
- Use a test account with exactly the target role.
- Check list and detail page.
- Check the desired action, for example Send, Save, Export or Delete.
- Check that a direct link doesn't grant more access than intended.
- Document role, test user, route and result.
Don't use the global administrator account for permission tests; it can hide missing rights.
How is this guide?
Manage the dashboard layout for team and roles
Arrange dashboard widgets as an administrator and apply them as the default for all employees or a role
Advanced navigation and quick actions configuration
Change the menu tree, visibility, sub-items, icons, external links, start tiles per role and the mobile bar in a controlled way