Manage roles, permissions and branch scope
Give staff enough authority to perform their work without granting access beyond assigned branches or your own authority.
Where this lives
- Settings › Roles
/dashboard/settings/roles
- Settings › Users
/dashboard/settings/users
Permissions needed
- Settings · Roles
- Settings · Users
Any one of these grants access. Ask an administrator if the screen is not visible to you.
Before you start
- Access to role or user administration
- A defined branch assignment policy
Complete the workflow
- 1
Define the role
Group permissions by job responsibility. Avoid combining cashier, finance administration and security administration without a business reason.
- 2
Respect delegation boundaries
You cannot grant permissions that you do not hold. Business-wide role definitions require access to all branches.
- 3
Assign branch access
Choose the user's home branch and additional allowed branches. Access All Branches is separate from an Admin role.
- 4
Verify the result
Ask the user to sign in again after authority changes, then confirm menus and record visibility from their account.
Useful tips
- A branch-limited administrator remains limited even when their role is named Admin.
- Review high-risk permissions periodically through the audit log.
Troubleshooting
Role definitions are read-only
The signed-in administrator lacks Access All Branches or does not have authority to delegate the selected permissions.
Related guides
Monitor registers and review variances
See active sessions, cashier ownership, expected cash, submitted counts and immutable manager reviews.
Configure the accounting foundation
Map operational events to the chart of accounts and control when financial periods accept postings.
Catalogue 2026.08.10