Use the standalone Letter Manager portal history
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 search a separate authenticated history page registered by Letter_manager_portal.
Where to goClient Area → Letter History menu (route letter_manager/letter_manager_portal/letter_history)
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
Search a separate authenticated history page registered by Letter_manager_portal. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Sign in to the client area.
- Go to Letter History.
- Search by reference, subject or verification code.
- Use Prev/Next when more than ten records exist.
- Go to View PDF or Verify.
Fields and options
Action scopeSearch a separate authenticated history page registered by Letter_manager_portal.
Module version1.0.0
Exact routeClient Area → Letter History menu (route letter_manager/letter_manager_portal/letter_history)
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- This controller redirects unauthenticated users to clients/login.
- It filters all queries by current client_id.
- It renders its own standalone HTML rather than the normal client theme layout.
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.