Roles and permissions

VoraSuite access is permission based, per product. There are no fixed user types: what a person can do follows entirely from the permissions their access level grants them in each product, at each site. You assign access levels from the user modal on the Team page at /access/users.

Permissions, not user types

Every action in the suite, such as viewing a register, capturing a result, editing master data or managing users, checks a specific permission. A person is not an operator or a manager by type; they are simply a user who does or does not hold the permission an action requires. This keeps access honest: the screen and the server enforce the same rule.

Access levels bundle permissions

You do not assign individual permission keys by hand. Each product offers named access levels, and each level is a bundle of permissions suited to a way of working, from view only through working levels up to product administration. Picking a level in the user modal grants that bundle for the selected product and site.

Per product and per site

Access is granted separately for VoraCore, VoraControl and VoraTool, and separately per site. The same person can be an administrator in one product and view only in another, or hold access at one site and none at a second. VoraAudit visibility follows the authorized products and the site entitlement rather than a per user assignment.

Floor kiosks derive from permissions

Floor kiosk mode is not a switch anyone flips. When the permissions of an account amount to capture only work, VoraSuite lands that account on the capture kiosk; when they amount to job card work only, it lands on the jobs kiosk. Broaden the permissions and the same account becomes a normal cockpit user. The behavior follows from the access level, nothing else.