Action-based permissions
Menu, button and page access are determined by fine-grained action permissions, not fixed roles.
- Module.action permission matrix
- Ready-made cashier/manager templates
- Fully custom role definitions
Users & Permissions
You decide who can see and do what
Permissions based on granular actions, not fixed roles. Let the cashier see only POS, the accountant only reports — fine-tuned permissions for every business.
- Action-based (module.action) permission system
- Ready-made roles or a fully custom permission set
- Branch-level user assignment
Who it's for
Is this module right for you?
- Businesses with more than one employee
- Chains and multi-branch operations
- Owners who want an audit trail
Before / after
Before Posmist
- Everyone sees everything
- Fixed roles aren't granular enough
- No trace of changes
With Posmist
- Module.action-based permissions
- Ready-made templates + custom roles
- Role/permission change history
How it works
Details
Secure access
Real permission checks happen server-side; hiding things in the UI is purely for user experience.
- Server-side permission validation
- Blocking unauthorized access attempts
- Session and device-level security
Auditability
User and role changes go into an append-only audit log — who changed what, and when, stays visible.
- Role/permission change history
- Per-user activity trail
- Compliant access records
FAQ
About Users & Permissions
Can a cashier see only POS?
Yes. The cashier template opens only the sales screen; reports and settings are hidden.
Does hiding a button in the UI provide real security?
The UI is purely for experience; the real permission check happens server-side and an unauthorized request is rejected.