Permissions by role
The customer asks: Each role sees and does only what it should
- Verdict: Ready, with limits (2)
- Door: Configure · area: Setup and administration › Roles, lists and data rules
- Recipe: none yet
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
Roles and permissions set up in iVendNext Desk.
Limits
- Permissions hide an action, never a field: hide some till fields with field rules (the card till-fields-shown-renamed-hidden).
- The kit has no recipe for permissions per till action.
Tell the customer
Each role is given only the actions it needs.
What next
- Tell the customer the 2 limits above, and write them into the proposal.
- Read how the door works: 4. Configure first.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
- Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.
Related needs
- Show our own fields on the till, call them by our words, hide the ones we never use — Ready, with limits (1)
- Cashiers count the drawer without seeing what the till expects — Ready
- A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
- One more detail on a line, for goods with no serial number — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need