Interpret pending and signed Letter Manager status
Follow this guide to use the signature icon in Sent Letters History without confusing it with email or postal status. 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 → Letter Manager → Sent Letters History → Status/action icons
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 you’ll accomplish
Use the signature icon in Sent Letters History without confusing it with email or postal status. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Find a letter with signature required.
- A pencil icon indicates no stored signature yet.
- A green check indicates a stored signature and includes signer name in the tooltip.
- Go to Verify or Internal Full View for full evidence.
Fields and options to review
Action scopeUse the signature icon in Sent Letters History without confusing it with email or postal status.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History → Status/action icons
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- No signature icon is rendered when require_signature is not set.
- The dashboard does not expose a separate signed status column.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.