Roles & Permissions

What are Roles?

A role defines what a team member can see and do in Cashvio. Each role has a set of permissions that control access to different features. For example, a "Cashier" role might only have permission to create orders, while a "Manager" role might have full access.

A role definition is not the same as an assignment. You define roles once, then assign one or more roles to each user. Each assignment is either business-wide (tenant scope) or limited to one store.

How Permissions Work

Cashvio has fine-grained permissions in the format action : resource, grouped by resource. The main groups are:

Scoped assignments and selected store

Operational pages (orders, inventory, POS, online store settings) evaluate permissions in the selected store context. A cashier assignment at Store A does not grant order access at Store B, even if the same person also holds another role elsewhere.

Business-wide (tenant-scoped) assignments apply across every store. Store-scoped assignments apply only at the chosen store.

A team member assigned to several stores works in all of them. Lists such as catalogue discounts, product reviews, store prices, product imports and store visits include every store where they hold the permission. Actions such as transferring stock work between any two of their stores.

The Tenant Admin built-in role is identified by a stable system key, not by its display name. At least one active administrator must remain; the portal blocks changes that would remove the last active admin.

Passing access on

You can only give out access you hold yourself, with the same reach:

• When you create or edit a role, you can include only permissions you hold business-wide.
• When you assign a role, you need all of its permissions business-wide for a business-wide assignment, or in that store for a store assignment.
• Creating a new store needs business-wide access to stores.
• Coupons and integrations follow their store: a team member with store-level access sees and manages only the coupons and integrations of their own stores.

How Roles Affect the Interface

When a user logs in, their assignments determine:

• Which sidebar menu items they see: Route access uses their combined assignments; store-bound actions respect the selected store.
• Which actions they can perform: Buttons like "New Sale" or "Delete Product" only appear when the permission holds in the current store context (or tenant-wide when no store is required).
• Which Dashboard quick actions appear: Only actions the user is allowed to perform are shown.