Installation, version, schema and module access

Understand message verification linkage

Understand why imported and automated messages can retain the verification session responsible for the event.

Audience: CRM administrators and deployment engineersPermission: AdministratorModule v1.0.0 · 2026.07.30-r20.5

Exact navigationAdmin Area → Setup → Modules

Before you begin

Confirm the module is active and select the intended WhatsApp account before changing any operational record.
Use an account with the stated native CRM capability and per-account access.
Test with controlled customer/contact data before relying on live verification, email or CRM automation.

What this guide covers

Understand why imported and automated messages can retain the verification session responsible for the event. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Exact step-by-step process

Open Admin Area → Setup → Modules.
Locate the account, conversation, setting, session or evidence relevant to “Understand message verification linkage”.
Review the displayed value or behaviour against this guide’s code-backed rules.
Do not change unrelated account, CRM or connector settings while verifying the result.
Confirm the expected state in the related Inbox, Connections, customer history, native CRM record or Audit Trail.

Fields, choices and supported possibilities

ModuleBritixo WhatsApp Web

Version1.0.0

Build2026.07.30-r20.5

CRM requirement3.0.*

Code-backed validations and workflow rules

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.
Understand why imported and automated messages can retain the verification session responsible for the event.

Expected result and verification

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.