Secure public access and e-signing

Open the secure public Delivery Note link

Follow this guide to use the tokenised recipient URL delivered by email or encoded in the PDF QR area. 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.

Audience: Delivery recipientsPermission: Secure token possessionModule v1.0.0
Jump to steps
Where to goRecipient email or Delivery Note QR code → Open secure link

What you’ll accomplish

Use the tokenised recipient URL delivered by email or encoded in the PDF QR area. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

  1. Go to the View & Sign Delivery Note link or scan the QR representation.
  2. Verify the reference, delivery date, recipient and delivered items.
  3. Check delivery notes and address.
  4. If status is Open, proceed to the signature section.
  5. If status is Signed, review the sealed confirmation instead.

Fields and options to review

  • Primary query-token URL generated by helper
  • Reference and status
  • Delivery data and item snapshot
  • Signature form only for unsigned records

Rules the system enforces

  • The public controller accepts a token from the route or `t` query parameter.
  • Opening a valid non-void note logs `viewed`.
  • No CRM login is required because the unguessable token authorises access.
  • The link does not expire in the supplied code.

How to confirm it worked

  • The intended recipient can review the delivery evidence without staff-portal access.

Safety checks and troubleshooting

  • Treat the URL as confidential; forwarding it grants the same public access.
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.