Run the Delivery Note security and operational checklist
Confirm least privilege, link protection, signing integrity and deployment readiness. 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 goAdmin Area → Delivery Note and Setup → Staff → Roles
What you’ll accomplish
Confirm least privilege, link protection, signing integrity and deployment readiness. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Check View/Create/Edit/Delete are assigned by least privilege.
- Verify module and invoice UI options are intentional.
- Test random token generation and HTTPS delivery in the deployed environment.
- Verify recipient links are not exposed in logs or public tickets.
- Test signed edit/void lock and void public blocking.
- Check SMTP, PDF, QR and client invoice access.
- Check event evidence and retention/uninstall procedure.
- Verify no backup/development artefacts are deployed as active code.
Fields and options to review
- Permissions
- HTTPS and secure bearer links
- CSRF/signature validation
- SMTP and PDF dependencies
- Client ownership/hash checks
- Event logging
- Retention and uninstall controls
Rules the system enforces
- The module relies on the hosting application and production TLS to protect public tokens in transit.
- Tokens have no built-in expiry/revocation.
- The public form does not independently verify signatory identity.
- The module should remain portable without core or server changes.
- Keep signing behind the supplied public controller because it performs the void-status check before calling the active model sign method.
How to confirm it worked
- The deployed feature is operationally controlled and its known limitations are accepted or mitigated.
Safety checks and troubleshooting
- Restrict access to signature data, IP addresses and bearer URLs as sensitive operational evidence.
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.