Understand the signed-confirmation email
This guide explains that what is sent after the model accepts the one-time signature. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAutomatic after Secure public Delivery Note link → Confirm Delivery
What you’ll accomplish
Know what is sent after the model accepts the one-time signature. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Complete the public signature.
- Wait for the sealed page.
- Check Recipient Email for Confirmation: Delivery Note {reference} Signed.
- Check signed time, IP and secure hash shown in the message.
- Use View Sealed Document to reopen the same note.
Fields and options to review
- Recipient Email stored on note
- Signed timestamp labelled UTC in email content
- IP address
- Full signature hash
- Sealed-document link
Rules the system enforces
- The confirmation is attempted only after the database update affects the note and the signed event is recorded.
- No confirmation is sent when Recipient Email is blank.
- The code does not attach the PDF.
- Email success/failure is not stored in a dedicated Delivery Note event.
How to confirm it worked
- The recipient receives an automated evidence summary and sealed-document link.
Safety checks and troubleshooting
- Do not treat mailbox delivery alone as proof that the recipient identity was independently verified.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.