Secure public access and e-signing

View a sealed signed Delivery Note

Reopen the public document after signing without exposing another signing form. 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: Valid token for a signed noteModule v1.0.0
Jump to steps
Where to goSigned confirmation email or original secure link → View Sealed Document

What you’ll accomplish

Reopen the public document after signing without exposing another signing form. 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 sealed-document link.
  2. Verify status Signed.
  3. Check delivery details, delivered items and notes.
  4. Check the recorded signature and secure hash information shown by the view.
  5. Save or print only through approved procedures.

Fields and options to review

  • Same secure token is retained
  • Public view is read-only after signed status
  • Signed confirmation content is displayed

Rules the system enforces

  • Reopening logs another `viewed` event.
  • The page does not offer a second signature.
  • The link has no built-in expiry or revocation in the supplied code.

How to confirm it worked

  • The recipient can revisit the sealed delivery evidence while the stored signature remains unchanged.

Safety checks and troubleshooting

  • Protect the link for as long as it remains usable.
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.