Customer profile and client portal

Use the standalone Letter Manager portal history

Search a separate authenticated history page registered by Letter_manager_portal.

Audience: Client contactsPermission: Logged-in client contactModule v1.0.0

Exact navigationClient Area → Letter History menu (route letter_manager/letter_manager_portal/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

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.

Exact step-by-step process

Sign in to the client area.
Open Letter History.
Search by reference, subject or verification code.
Use Prev/Next when more than ten records exist.
Open View PDF or Verify.

Fields, choices and supported possibilities

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.

Code-backed validations and workflow rules

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.

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.