The everyday problem
Permissions should be verified from the account that staff will use. An owner demonstration can show actions that a cashier is not intended to perform, so it does not establish whether the working role is configured correctly.
A workable process
List permitted actions for each role, including any rate-edit or discount limits needed by the business. Sign in as a sample cashier and try a normal sale plus an action that should require permission. Have the owner review the observed result.
A practical example
A manager may be allowed to change a rate while a temporary cashier is not. If everyone shares the manager login, the configuration no longer separates those responsibilities. Individual accounts also give the team a clearer basis for reviewing who performed a transaction.
Before you finish
Test both allowed and disallowed actions. Keep credentials private, review access when staff change roles and confirm the supported controls with the product team rather than assuming every action has a separate permission.
Try this check with your team
Sign in as the cashier and try an allowed sale, a rate change and a discount above the intended limit. Repeat with the appropriate manager account. Record the actual outcome rather than relying only on the administrator’s settings screen.
What the result tells you
The role is ready when permitted work succeeds and restricted actions behave as intended in that exact workflow. Recheck permissions when a new branch, user role or billing path is introduced.
See this workflow in Speed Plus.
Bring a sample transaction and your questions to a product demo.
Book a free demo ↗