Understand notification logging
Trace emails as events linked to an entity and recipient.
Exact navigationTechnical reference → Courier model sendNotification
What this guide covers
Trace emails as events linked to an entity and recipient. 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 Technical reference → Courier model sendNotification.
- 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
EventDispatch, POD request/completion, daily digest or related module event.
Entity/IDSource record identity.
RecipientTarget email.
Subject/bodyGenerated message content.
Result/timeDelivery attempt evidence.
Code-backed validations and workflow rules
- A send log proves an attempt/result, not that a human read or accepted the message.
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.