Install and activate Email Marketing & Newsletter
Follow this guide to create the campaign and recipient tables and register the Letter Manager tab and cron hook. 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 → Setup → Modules → Email Marketing / Newsletter → Activate
Before you start
- 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 you’ll accomplish
Create the campaign and recipient tables and register the Letter Manager tab and cron hook. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Upload the module directory under the CRM modules directory.
- Go to Setup → Modules.
- Find Email Marketing / Newsletter and select Activate.
- Go to Letter Manager and confirm the new tab appears.
- Run the CRM cron once and verify no module-table error is logged.
Fields and options to review
Action scopeCreate the campaign and recipient tables and register the Letter Manager tab and cron hook.
Module version1.0.0
NavigationAdmin Area → Setup → Modules → Email Marketing / Newsletter → Activate
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Activation runs install.php and creates the two module-owned tables.
- No separate deactivation or uninstall cleanup hook is registered in the supplied code.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.