Dispatchers & Permissions

Dispatchers are your operational staff — the people who answer the phone, create bookings, and assign drivers. What makes them safe to onboard is the permission matrix.

The permission matrix

Open a dispatcher from the roster to see their profile and System Permissions card:

Every area of the plugin is listed — Dashboard, Bookings, Draft Bookings, Quotes, Booking Forms, Airports & Airlines, Vehicles, Drivers, Track Drivers, Settlement, Customers, Invoices, Revenue, Email Templates, Email Log, and Settings — sixteen in all. Each one gets one of three levels:

• Off — the area disappears from the dispatcher's menu entirely.
• Read — they can open and view, but every create/edit/delete control is blocked.
• Write — full access to that area.

Click Edit, set the levels, Save. Changes apply immediately.

Enforced everywhere

This isn't menu-hiding. The same permission map is enforced by the REST API on every request, so a read-only dispatcher can't modify data even with crafted requests. In the interface, write-guarded buttons explain themselves rather than failing silently.

Typical setups

• Phone dispatcher — Bookings/Quotes/Customers write, Drivers/Vehicles read, everything financial off.
• Accountant — Invoices/Revenue/Settlement write, Bookings read, the rest off.
• Night shift — Bookings write, Track Drivers read, all configuration off.

Managing the account

The profile card edits contact details, pauses the account (blocks portal sign-in without deleting anything), re-sends the set-password email, and deletes the dispatcher.