Roles & permissions
The five named roles in Routel and what each can see and do.
Every user in Routel has exactly one role. The role decides which modules they see, which records they can open, and which actions they can perform. The same rules apply in the web interface and in the AI Assistant: asking the assistant for something outside your role produces a polite refusal, not a workaround.
The roles
| Role | Typical person | Sees and does |
|---|---|---|
| Admin | Owner, IT | Everything, plus user management, roles, and settings such as expense categories. |
| Management | Directors, GMs | All jobs and every report: P&L, cash position, aging, customer profitability. |
| Accounting | Finance team | Invoices, payments, credit and debit notes, credit limits, statements, expenses and payroll, the General Ledger and all financial reports. |
| Operations | Ops executives | Jobs, bookings, containers, Bills of Lading and shipment documents. |
| Sales | Sales executives | Route rates, quotations, and the jobs that belong to their customers. |
Enforcement
Permissions are checked on the server for every request. Hiding a button in the interface is a convenience; the actual rule lives behind it. This matters for the assistant in particular: it calls the same server actions as the interface, so it inherits the same checks.
Who can do this
Only Admin can create users, assign roles, or add expense categories.
Audit log
Every job keeps a log of who changed what and when. Actions taken through the assistant are recorded with the name of the person who confirmed them, not as "the assistant", so the trail stays accountable.