Customer profile and client portal

Open Letter History from a customer profile

Review letters linked to one CRM customer inside the admin profile.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Customers → Open customer → Letter History

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 letters linked to one CRM customer inside the admin profile. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open the customer.
Select Letter History.
Search or page through the customer’s letters.
Open View PDF or Verify.
Review email/read and postal evidence.

Fields, choices and supported possibilities

Action scopeReview letters linked to one CRM customer inside the admin profile.

Module version1.0.0

Exact routeAdmin Area → Customers → Open customer → Letter History

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

The tab calls get_history_by_client(client_id).
External letters with client_id=0 do not appear.

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.