Understand deactivation and removal limitations

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Avoid assuming that the supplied release automatically removes its database tables or campaign data.

What this guide helps you do

Avoid assuming that the supplied release automatically removes its database tables or campaign data. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

1. Export or retain any campaign evidence required by policy.
2. Deactivate the module only through Setup → Modules.
3. Check the Letter Manager tab and cron handler stop loading.
4. Use an approved database change only if the organisation intentionally removes retained module data.

Fields and options

Rules and limits

• The supplied code has an activation hook but no registered deactivation or uninstall cleanup hook.
• Do not manually drop tables as part of routine deactivation.

Check 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.

Related guides