Handle job notifications and recipient merging
Understand who can receive dispatch, status and POD emails.
Exact navigationAdmin Area → Courier & Logistics → Jobs / Delivery Notes
What this guide covers
Understand who can receive dispatch, status and POD emails. 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
- Open Admin Area → Courier & Logistics → Jobs / Delivery Notes.
- Review the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields, choices and supported possibilities
DriverSaved valid driver email.
ReceiverSaved receiver email.
CustomerPrimary customer email and notification list.
OperationsConfigured operations email.
POD recipientExplicit recipient on the delivery note.
Code-backed validations and workflow rules
- Recipients are merged and de-duplicated for the applicable event.
- Only authorised addresses should be stored.
- Notification logs provide delivery evidence; they do not prove the recipient acted.
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.