Handle job notifications and recipient merging

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains who can receive dispatch, status and POD emails.

What this guide helps you do

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.

Follow these steps

1. Go to Admin Area → Courier & Logistics → Jobs / Delivery Notes.
2. Check the source record and choose the supported action.
3. Save or submit once, then reopen the record and verify the result.

Fields and options

Rules and limits

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

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.

Related guides