Role-based Access

Six roles, enforced the same way everywhere

Admin and Management see every module, narrowing only at system configuration. Accounting owns Finance, Reports and Expenses, Sales and Pricing own Quotations, Operations owns the Bill of Lading, and Operations and Sales edit bookings — which every signed-in member of staff can read.

6

named roles

1

set of rules, enforced the same in the UI and the AI assistant

Without it

What this usually looks like

Permissions configured as checkboxes on a settings screen drift out of sync with what's actually enforced underneath.
The AI assistant quietly has more (or less) access than the person using it, because it was wired up separately from the real permission system.
Walling off entire modules by department means people constantly asking for exceptions just to get their work done.
Permissions are checked on the server for every request, by the same rules whether the action came from a screen or from a sentence typed into the assistant — narrowing only the specific sensitive modules, not the whole product.
What's built in

Everything this module does

Six named roles

Admin, Management, Accounting, Operations, Sales, Pricing — each with a clear, specific scope — plus general staff.

Admin and Management see everything

The only difference: system configuration (users, roles, settings) stays Admin-only.

Narrow, specific gates

Accounting → Finance, Reports & Expenses; Sales/Pricing → Quotations; Operations → Bill of Lading; Operations/Sales → editing bookings.

Open by default elsewhere

Any signed-in staff can read bookings, and Business Partners, Documents and the Labeling Center are open to everyone.

How it works

From first step to done

01

A user signs in

With exactly one role.

02

Every request is checked

Server-side, for every screen and every assistant action.

03

The same rule, every path

A UI click and an assistant request hit the identical permission check.

Who uses this

Built around real roles, not generic permissions

Admin

Every module, plus user management and system configuration.

Management

Every module Admin sees, except system configuration.

Accounting / Operations / Sales / Pricing

Each gated to their specific sensitive modules, open elsewhere.

Questions we get asked

Can the assistant do something a user couldn't do manually?

No — it acts as the signed-in user and is checked against the exact same role rules.

Does every module require a specific role?

No — only the ones explicitly gated. Most of the product is open to any signed-in staff member.

Who can create users or change roles?

Only Admin.

See Role-based Access running on a real booking

A 30-minute walkthrough on your own routes and workflow, not a generic slide deck.

Request a demo