Skip to content

Permissions

All employee permissions are listed in a table on the Permissions page:

ID Employee number
Employee Employee name
Clean Drawers Can this employee count and mark cash drawers as clean?
Open A/R Account Can this employee create an A/R account?
Change Credit Limit Can this employee change, add, or remove customer credit limits?
See Sensitive Numbers Can this employee view sensitive financial figures — sales totals, payment breakdowns, labor data — on reports? Without it, most reports hide their dollar amounts.
Apply Payments Can this employee apply customer payments to outstanding A/R balances?
Close Orders Can this employee close purchase orders?
Void Sales Can this employee completely undo a sale via the "void all" button?
Add Depts Can this employee add new inventory departments?
Edit Inventory Can this employee make changes to inventory? (Prices, descriptions, etc.)
Order Can this employee build, submit, make changes to, or receive purchase orders?
Merge Customers

Can this employee merge two customer accounts into one?
Can this employee change a customer's class? (Make a retail account a landscaper)

No Sale Can this employee use the "No Sale" button to open the cash drawer?
Discount Can this employee apply manual discounts at the register?
Edit Order Points Can this employee edit order points of an item for the order recommendations report?
Edit the employee permissions

Info

We can make all reporting require admin credentials upon request- let us know!

How a permission is decided (Yes / No / Inherit)

Each employee permission has three possible settings:

  • ✅ Yes — explicitly granted to this employee.
  • ❌ No — explicitly denied to this employee.
  • Inherit from group — the employee has no setting of their own, so VMX uses their group's setting instead. If the group doesn't have a setting either, the permission defaults to No.

In the permissions table, an asterisk after the value (✅ * or ❌ *) means that value is inherited from the employee's group rather than set on the employee directly. To override an inherited value, set the employee's own permission to Yes or No; to go back to following the group, set it to Inherit from group.

Permission groups

Groups act as permission templates. Set up a group once with the permissions that role should have, then assign employees to it — each employee follows the group's settings automatically unless you override a specific permission on that employee.

A typical setup uses a small number of groups, for example:

  • Cashier — register basics; no voids, no discounts, no No Sale.
  • Senior Cashier — adds Discount.
  • Supervisor — adds Void Sales, No Sale, and Clean Drawers.
  • Manager / Owner — everything, plus admin access (see Admin Permissions).

When someone changes roles, moving them to a different group updates all their inherited permissions at once.