Permissions are more than showing or hiding a screen. Module access and action permission are granted separately: a user can see stock but not delete a voucher, or open the finance list without editing a payment voucher.
Modular licensing switches a capability on for the account; permissions decide who uses it. Set up both together.
Who is it for?
IT and system admins build the role templates. Managers in finance, e-documents and HR want actions separated. A branch manager runs the team in their scope, a central user sees more. Firms that must answer "who did what?" start here.
How it works
Users receive roles; roles carry module and action permissions. Typical permissions cover read, create, update, delete, and approval/special actions. The same user may work with different rights across company or branch scopes; configured with multi-company, branch, warehouse.
Company and system management screens administer users, roles, and permissions. New hires start from templates (warehouse operator, sales rep, accounting); exceptions are narrowed or widened per user. Sensitive actions (invoice cancel, bank movement, e-document send) are protected with separate permission rows.
Mobile and web use the same permission model, so the field isn't over-granted and the office isn't needlessly locked. B2B buyer accounts stay within their portal scope and don't mix with platform user permissions.
Review leavers and role changes regularly, especially for finance and e-document permissions.
Benefits
Access by task replaces "everyone is admin". Users only see the menus they need, which also shortens training. In privacy-sensitive areas such as CRM outreach and opt-out, it is clear who can reach what. Branch separation keeps central data from spreading more than necessary.
Relation to modules and products
Permissions apply in every licensed module, from stock vouchers to CRM activities and from POS shifts to finance collections. Definitions live in Company. You manage permissions on Platform Web and Mobile applies the same ones. Keep integration agent accounts under control too; write access to your existing system is especially critical.
FAQ
If a license is open, can everyone use it? No. Licensing opens the capability on the account; users still need roles and action permissions.
Are role templates required? Templates accelerate setup; custom roles are allowed. Starting with a few standard roles is practical.
Can a branch manager see another branch? Only according to scope and permission definitions. Multi-company/branch scope is set with authorization.
Is there a separate mobile permission model? No. The permission logic is the same; only the channel license and screens may differ.
Next step
Draft four to six roles: read-only, operator, approver, admin. Mark sensitive actions separately. Try Free to set them up in your account, then connect multi-company scope.