Setup, access and Letter Manager integration

Verify Letter Manager dependencies

Confirm the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAdmin Area → Letter Manager
Before you begin
  • Use an authorised account and confirm the source CRM record or setting is correct.
  • Follow the exact route shown above; do not force database values to imitate a completed action.

What this guide covers

Confirm the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Open Letter Manager.
  2. Confirm the normal Letter Manager tabs and template dropdown load.
  3. Select the newsletter tab.
  4. Confirm the module can read the existing template dropdown and initialise its editor.

Fields, choices and supported possibilities

Action scopeConfirm the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace.
Module version1.0.0
NavigationAdmin Area → Letter Manager
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • The module looks for #template_id_external and falls back to #template_id.
  • Predefined template copying depends on data-subject and data-letter-body attributes on the Letter Manager options.

Expected result and verification

  • The requested record, output or setting is created or updated through the supported module flow.
  • Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
  • An error message is investigated rather than bypassed.

Security, privacy and operational checks

  • Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
  • Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
  • Test configuration changes with controlled records before production-wide use.
  • Retain or delete evidence only under an authorised retention process.