Delete a Letter Manager template
Remove a reusable template without deleting letters already created from it. 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.
Where to goAdmin Area → Letter Manager → Templates → Delete icon
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
Remove a reusable template without deleting letters already created from it. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Verify the template is no longer required.
- Select the red delete icon.
- Verify the CRM deletion prompt when shown.
- Check the template is absent from the table and send-form selectors.
Fields and options to review
Action scopeRemove a reusable template without deleting letters already created from it.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Templates → Delete icon
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 delete action deletes the template row by ID.
- Letter history rows store their own subject and content, so prior letters are not linked back to the template.
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.
Important code-backed limitationThe supplied delete route has no recycle bin or template-version recovery.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.