Templates and content authoring

Understand Letter Manager template fields

Keep the internal template label separate from the recipient-facing subject and PDF content. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Templates → New/Edit Template

Before you start

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 you’ll accomplish

Keep the internal template label separate from the recipient-facing subject and PDF content. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Use Template Name to help staff identify the template.
Use Letter Subject for the correspondence subject.
Use Letter Content for the official PDF body.
Save and test the template in both send tabs.

Fields and options to review

Action scopeKeep the internal template label separate from the recipient-facing subject and PDF content.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Templates → New/Edit Template

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules the system enforces

The templates table retains template_name, subject and content.
The historical name field may exist from the base table, but the current UI uses template_name.
The module does not expose merge-field validation or a separate version history for templates.

How to confirm it worked

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.

Was this guide useful?Your response is stored only in this browser.