Understand the Courier menu and exact navigation paths
Follow this guide to use the code-registered menu labels to reach every workspace.
Where to goAdmin Area → Courier & Logistics
What this guide helps you do
Use the code-registered menu labels to reach every workspace. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to Courier & Logistics in the left navigation.
- Select the workspace whose label matches the task.
- Use the record-level action only after checking permission and status.
Fields and options
DashboardSummary, flow counts and recent jobs.
Live OperationsOperational snapshot and current activity.
Live JobsProvider jobs available for review/import.
JobsInternal job register and job detail.
DispatchAssignment workspace; Dispatch permission required.
DriversDriver records, pay profile and documents.
VehiclesFleet records and compliance dates.
CustomersCourier customer records and CRM sync.
Delivery NotesPOD requests, signatures and snapshots.
ComplianceDriver and vehicle alerts; compliance permission required.
FinanceSettlements, expenses, invoices, journals; finance permission required.
Instant ReportFiltered company/driver/vehicle/client/provider reporting.
SettingsModule, provider and BP fuel configuration; integrations permission required.
Rules and limits
- Use the supported screen and permission; do not bypass validation or edit database records directly.
Check it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Related guides
Was this guide useful?Your response is stored only in this browser.