Require an e-signature on an external letter
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to send a public signature link to the external email recipient.
Where to goAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Require Recipient to E-Sign this Document
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
Send a public signature link to the external email recipient. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Enter a valid recipient email.
- Select the signature checkbox.
- Generate and email the letter.
- Ask the recipient to use the Review & Sign Document link.
- Check the signed state and acceptance evidence.
Fields and options
Action scopeSend a public signature link to the external email recipient.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Require Recipient to E-Sign this Document
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- A signature link is added to the email only when require_signature=1.
- If no email is supplied, the record still receives a hash but the module cannot deliver the signature link automatically.
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.