Understand Letter Manager signature evidence
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 review the stored image and signer metadata after acceptance.
Where to goAdmin Area → Letter Manager → Sent Letters History → Internal Full View / Verify
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
Review the stored image and signer metadata after acceptance. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to the signed letter.
- Check the signature image.
- Check signer first name, last name and email.
- Check acceptance date/time and IP address.
- Compare the reference and content with the issued PDF.
Fields and options
Action scopeCheck the stored image and signer metadata after acceptance.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History → Internal Full View / Verify
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 signature filename is {hash}_signature.png.
- acceptance_date is the server time at submission.
- acceptance_ip is the CodeIgniter input IP address.
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.