Customer profile and client portal

View a letter from the client area

Open a single customer-linked record after server-side client ownership validation.

Audience: Client contactsPermission: Logged-in client contact for the linked customerModule v1.0.0

Exact navigationClient Area → Letter History → View

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

Open a single customer-linked record after server-side client ownership validation. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open Letter History.
Select View for the required record.
Review the subject/content and QR verification presentation.
Return to My Letters when finished.

Fields, choices and supported possibilities

Action scopeOpen a single customer-linked record after server-side client ownership validation.

Module version1.0.0

Exact routeClient Area → Letter History → View

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 controller requires both letter ID and client_id=get_client_user_id.
A record belonging to another customer returns 404.

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.