Roles vs module access

Two things decide what a team member can do:

1. Role — a tier: Owner, Admin, Manager, Salesman or Cashier. It sets the ceiling.
2. Module access (optional) — a matrix giving each section No access, View or View & edit. It can only narrow what the role allows.

A request must pass both checks. The server enforces them on every call, so hiding a section in the menu is backed by a real refusal, not just a missing link.

The role ladder#

Some sections are also hidden below a minimum role regardless of the matrix — for example POS, Reports and Finance need Manager, and Team & Access and Settings need Admin. See the table in How the app is organised.

Access without a matrix#

A member with no custom matrix gets the access their role implies:

The three presets#

The Team page offers three one-click levels. Each sets the matrix for every module at once:

Change any single cell and the member shows as Custom.

How a custom matrix sets the role#

Because every screen also checks the role, the app keeps the two consistent automatically when you save a matrix:

• View & edit on Team & Access or Settings → the member becomes Admin.
• Otherwise, View & edit on any module → Manager.
• Only View / No access everywhere → Cashier (read-only).

Those two modules carry a warning in the matrix because edit access to them is administrative power over the whole workspace.

Special modules#

When changes take effect#

Access is checked on every request, not stored in the member's session. A change applies within about a minute — and immediately on the member's next request in most cases — without them signing out.

Error messages#

Related#

• Roles
• Module access matrix
• Inviting & managing members