Understand Letter Manager menu and hook integration
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that where the module appears for staff, customer profiles and logged-in clients.
Where to goAdmin Area → Letter Manager; Admin Area → Customers → Open customer → Letter History; Client Area → 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
Know where the module appears for staff, customer profiles and logged-in clients. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to the staff sidebar and confirm Letter Manager with Dashboard, Templates and Settings.
- Go to a customer profile and select Letter History.
- Sign in as a client contact and confirm Letter History appears in the client menu.
Fields and options
Action scopeKnow where the module appears for staff, customer profiles and logged-in clients.
Module version1.0.0
Exact routeAdmin Area → Letter Manager; Admin Area → Customers → Open customer → Letter History; Client Area → 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
- The staff sidebar uses the letter-manager parent with three children.
- The admin customer-profile tab is registered at position 50.
- The client menu item is added only when a client contact is logged in.
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.