Understand postal update audit fields
Review which staff member last saved postal details.
Exact navigationAdmin Area → Letter Manager → Internal Full View / authorised record inspection
Before you begin
- 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 covers
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.
Exact step-by-step process
- Review postal status, courier, tracking code and posted date.
- Review Posted By Staff ID.
- Resolve the staff ID to an account for an authorised audit.
Fields, choices and supported possibilities
Action scopeReview 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.
Code-backed validations and workflow rules
- 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.
Expected result and verification
- 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.