Understand signature-link lifecycle limitations
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Plan for public links that have no built-in expiry, revocation or resend-specific rotation.
Where to goLetter Manager signature and verification links
Before you start
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What this guide helps you do
Plan for public links that have no built-in expiry, revocation or resend-specific rotation. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Record when the correspondence was sent.
- Revoke access through an approved code/data process only when legally and technically authorised.
- Do not assume Resend Email changes the public hash or unique code.
- Use a stronger signing platform when expiring links are mandatory.
Fields and options
Action scopePlan for public links that have no built-in expiry, revocation or resend-specific rotation.
Module version1.0.0
Exact routeLetter Manager signature and verification links
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- The hash and unique_code are created once with the history row.
- Resend Email reuses the stored values.
- No expiry timestamp, revoked flag or token-rotation action is implemented.
Check it worked
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Related guides
Was this guide useful?Your response is stored only in this browser.