Templates and content authoring

Understand Letter Manager template access limitations

Do not assume create, edit or delete is protected by a dedicated template capability.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Templates

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

Do not assume create, edit or delete is protected by a dedicated template capability. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Restrict staff who can access Letter Manager through organisational access controls.
Use an authorised role to manage templates.
Audit template changes operationally because the supplied UI does not show template change history.

Fields, choices and supported possibilities

Action scopeDo not assume create, edit or delete is protected by a dedicated template capability.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Templates

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

Templates extends AdminController but performs no module-specific staff capability check.
All authenticated staff who can reach the route may be able to create, update or delete templates.

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.