Granting Permissions
Authority on the Mobile POS is set per person, not per role, and an administrator grants a right by ticking it on that person's permission sheet in iVendNext Desk. This page covers how a grant works, how it then appears for the operator, and the rights that reach nobody on the phone until you grant them.
Prerequisites
- You can edit the person's permission sheet in iVendNext Desk. This is an administrator task, not a job done from the phone.
- You know who needs which right. Some grants change the phone alone, and some change iVendNext Desk as well, so decide the change with the person's whole role in mind.
How authority works here
Authority is per person. Each person has one permission sheet linked to their account, and that sheet decides what they may do, on the phone and in iVendNext Desk alike. A person with no sheet linked has almost none of the rights that live on it.
Rights are not tied to a job title. The phone never checks a role name to decide what someone may do. It reads the person's own sheet instead, so the same title can carry different authority in two stores, and a store can change a person's authority without a release.
Granting a right
- In iVendNext Desk, open the person's permission sheet.
- Find the section for the rights this product adds. It sits in its own clearly named block, after iVendNext Desk's own fields.
- Tick the right you want to grant.
That is the whole change. Nothing is deployed, and there is no release involved.
How the grant appears for the operator
The grant takes effect on the operator's next read. They do not need to be signed out and back in for most changes, though signing in afresh is the surest way to pick a change up at once.
The server is what decides, every time. A hidden button is never the only check. Even where a control does not appear, the right is still checked at the point of action, and a request made without the right is refused with a message that names what is missing. So an operator who has just been granted a right will find the action allowed, and one whose right was removed will be told plainly, rather than failing without a reason.
The two ready-made permission sets
Two sets ship with the product, named Cashier and Manager. Both carry the ordinary selling, shift, return, void, gift-card, on-account, quotation, and order rights, and both carry discount and price caps: the Cashier set at half, the Manager set at full. Neither set carries any of the rights this product adds.
Two rights differ between the sets, and one of the differences surprises people. The register read is off for Cashier and on for Manager, which is what you would expect. Opening the cash drawer is on for Cashier and off for Manager, which is not. That is iVendNext Desk's own shipped position, and the phone follows it rather than quietly correcting it. If your managers need to open a drawer, tick it. It is a one-tick change, and it is not a defect.
Rights no operator has until you grant them
After a fresh install, six of the rights an operator would use from the phone reach no operator at all. This is a go-live checklist, not a fault list.
| Right | Why it is not held |
|---|---|
| Applying the staff discount rate to an employee's own purchase | Neither ready-made set ticks it |
| Entering a weight by hand when the scale cannot give one | Neither ready-made set ticks it |
| Taking a return with no original receipt | Ships denied on purpose. See below |
| Turning a till's cash drawer on or off from the phone | Neither ready-made set ticks it. The default leaves it to head office |
| Retiring a phone | Ships unticked deliberately, and only a system administrator can tick it |
| Administering staff badges | Has no phone grant at all. It is done in iVendNext Desk |
One of these is a policy, not an oversight. Taking returns without the original sale is a known refund-fraud route, so the product ships it denied, and expects a store to grant it person by person. Until you do, every receipt-less return is escalated to a manager, which is the behavior working rather than a gap. The associate's side of that request is on Returning Without a Receipt.
Two rights go the other way, and are worth knowing for the same reason. Layaway ships switched on, so a store that does not want it unticks it. Freeing up a busy till is switched on once for the Manager set when the product is installed, so a manager can release a claimed register when every till at the store is taken. That task is on Starting Your Day.
Which rights a manager cannot grant to themselves
Retiring a phone is the one exception to the rule that a manager may edit permission sheets. It sits at a raised permission level, so the managers it bounds cannot tick it on themselves. Only a system administrator can grant it.
Read the boundary precisely. It stops a manager granting this one right upward, and it is not a general ranking between managers. Every other right this product adds stays manager-editable, exactly as iVendNext Desk already allows. A system administrator can already retire a phone in iVendNext Desk, so granting the right on the phone is about delegating that authority to a named manager, not about creating it. What retiring a phone does, and how to handle a lost or stolen one, are on Managing Devices.
Three rights that are not on the sheet at all
A few rights are ordinary record permissions, granted through the usual role tooling rather than by ticking a box on a person's sheet.
| Right | Who carries it as shipped |
|---|---|
| Deciding an approval | The manager role that ships with iVendNext, and the system administrator |
| Administering staff badges | The system administrator alone |
| Editing a customer | The cashier role that ships with iVendNext |
Retiring a phone can be granted either way: by the switch above, or by a record permission. Both routes are honored.
What else a tick changes
Unticking a right on the sheet is not a phone-only act. Most of the rights the phone reads are iVendNext Desk's own fields, so the change takes effect on both the phone and iVendNext Desk at once. Only the small set this product adds changes the phone alone.
The reverse is the sharper trap. Several of iVendNext Desk's own fields are ones it ships and then does not consult, but the phone gives them real effect. Turning one off changes nothing a manager can see in iVendNext Desk, and changes what an operator can do on the phone. So test a grant change on the phone, and do not infer it from iVendNext Desk.