Upload and activate the module

Install the ZIP through the native module manager and allow the activation hook to create or upgrade the module-owned schema. 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.

What you’ll accomplish

Install the ZIP through the native module manager and allow the activation hook to create or upgrade the module-owned schema. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

1. Go to Admin Area → Setup → Modules.
2. Upload the supplied installable ZIP without renaming its internal module directory.
3. Find Britixo WhatsApp Web and select Activate.
4. Wait for activation to complete, then open Admin Area → WhatsApp → Connections.

Fields and options to review

Rules the system enforces

• Activation runs the idempotent, prefix-aware installer.
• Normal administration does not expose connector URLs, ports, tokens, Node.js or shell commands.
• The module uses linked-device WhatsApp Web sessions rather than the WhatsApp Business API, Cloud API or Meta Graph API.
• Install the ZIP through the native module manager and allow the activation hook to create or upgrade the module-owned schema.

How to confirm it worked

• The requested action completes without a permission, validation, connector or native CRM error.
• The selected account or conversation shows the expected state without changing another account’s data.
• Where the action creates evidence, confirm the message, native record, verification event, portal history or audit entry is present.

Security, privacy and troubleshooting checks

• Never expose connector tokens, loopback ports, authentication directories or raw customer verification replies.
• Use the supported Connections, Access Control, Settings and Audit Trail pages rather than editing runtime or database records directly.
• If the expected control is missing, verify both native capability and per-account permission before treating it as an installation fault.

Continue with related guidance