Understand postal update audit fields
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 which staff member last saved postal details.
Where to goAdmin Area → Letter Manager → Internal Full View / authorised record inspection
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 which staff member last saved postal details. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Check postal status, courier, tracking code and posted date.
- Check Posted By Staff ID.
- Resolve the staff ID to an account for an authorised audit.
Fields and options
Action scopeCheck which staff member last saved postal details.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Internal Full View / authorised record inspection
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- Every single or bulk save sets posted_by_staff_id to the current staff user.
- The code does not keep a version history of earlier postal values.
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.