Apply privacy controls to newsletter evidence
Handle campaign content, recipient data, IP addresses and user agents under authorised privacy and retention rules.
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter → History
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
Handle campaign content, recipient data, IP addresses and user agents under authorised privacy and retention rules. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Use a lawful approved audience.
- Limit access to authorised staff.
- Avoid placing unnecessary sensitive data in subject/body.
- Apply organisational retention and deletion procedures to campaign tables when required.
- Explain tracking-image limitations in relevant notices.
Fields, choices and supported possibilities
Action scopeHandle campaign content, recipient data, IP addresses and user agents under authorised privacy and retention rules.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → History
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The module stores recipient identity, email, delivery errors, open IP/source and user agent.
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.