Understand invalid, missing and void public-link errors
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Interpret each access-denied branch implemented by the public controller.
Where to goSecure public Delivery Note link
What this guide helps you do
Interpret each access-denied branch implemented by the public controller. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- If the page says Invalid Request, check whether the link includes its token.
- If it says Document Not Found, request a fresh exact link from authorised staff and verify the note exists.
- If it says Document Voided, contact the sender for the replacement note.
- Do not retry by altering token characters.
Fields and options
- Missing/blank token → Invalid Request
- Unknown token → Document Not Found
- Known note with status void → Document Voided
- Valid open/signed token → public document
Rules and limits
- The controller does not disclose another record when the token is wrong.
- Void status is checked before rendering or signing.
- A signed link remains viewable in sealed mode.
- There is no token-expired message because expiry is not implemented.
Check it worked
- Users receive a safe, specific outcome without revealing unrelated delivery data.
Safety checks and troubleshooting
- Support should verify the note from the admin register rather than ask the recipient to share the full token publicly.
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.
Related guides
Was this guide useful?Your response is stored only in this browser.