Module setup, access and navigation

Configure the optional Courier dashboard replacement

Decide whether authorised staff should land on the Courier dashboard instead of the standard staff dashboard.

Audience: Courier operations staffPermission: Courier: Manage integrationsModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Settings → General

What this guide covers

Decide whether authorised staff should land on the Courier dashboard instead of the standard staff dashboard. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Exact step-by-step process

  1. Open Settings.
  2. Locate the standard staff dashboard replacement option.
  3. Enable it only for the intended operational deployment.
  4. Save settings.
  5. Test with a non-administrator staff account.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

  • The replacement hook applies only where the module’s request and permission conditions are satisfied.
  • Keep a supported navigation route back to the normal CRM features required by staff.

Expected result and verification

  • 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.