Understand the signed-confirmation email
Know what is sent after the model accepts the one-time signature.
Exact navigationAutomatic after Secure public Delivery Note link → Confirm Delivery
What this guide covers
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.
Exact step-by-step process
- Complete the public signature.
- Wait for the sealed page.
- Check Recipient Email for Confirmation: Delivery Note {reference} Signed.
- Review signed time, IP and secure hash shown in the message.
- Use View Sealed Document to reopen the same note.
Fields, choices and supported possibilities
- Recipient Email stored on note
- Signed timestamp labelled UTC in email content
- IP address
- Full signature hash
- Sealed-document link
Code-backed validations and workflow rules
- 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.
Expected result and verification
- The recipient receives an automated evidence summary and sealed-document link.
Checks, security 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.