Installation, version, schema and module access

WhatsApp Web Messaging

Britixo WhatsApp Enterprise: complete how-to guide

Understand WhatsApp Web Messaging

Review the shared linked-device inbox, account isolation, verification, automation, CRM conversions, portal history and audit design delivered in build r20.5.

Check the CRM version requirement

Confirm the CRM is compatible with the module header requirement of version 3.0.* before activation.

Understand module version 1.0.0 and build r20.5

Distinguish the semantic module version from the dated release build that contains registered-mobile recognition and administrator customer-history improvements.

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.

Understand the activation hook

Understand that activation loads the helper and install.php, then runs the idempotent installation function.

Understand automatic schema upgrades

See how every request can call ensure_installed so an older installation is brought to the current schema without a manual database command.

Review the eleven module-owned tables

Understand the accounts, access, conversations, messages, standard replies, reply visibility, conversions, audit, verification sessions, verification events and automation-session tables.

Understand prefix-safe database installation

Confirm all table names use the current CRM database prefix and can therefore work in installations that do not use the default prefix.

Understand account schema additions in r20.5

Review event-stream identity, deletion metadata and connector-cursor fields used for safe live-event recovery and soft deletion.

Understand conversation verification fields

Review verification session, verification status, verified contact and verified customer fields stored on conversations.

Understand message verification linkage

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

Understand the module hooks

Review administrator menus, portal menus, customer-profile history, assets, cron synchronisation and runtime watchdog hooks.

Understand native module capabilities

Distinguish View, Manage standard replies and Audit Trail capabilities from the separate per-account permission matrix.

Understand menu visibility rules

Learn why Inbox, Standard Replies, Connections, Access Control, Settings and Audit Trail appear for different users.

Open the WhatsApp administrator workspace

Use the WhatsApp sidebar group and select the workspace permitted for the signed-in staff member.

Verify installation after activation

Confirm the WhatsApp menu, Connections page, schema build option, assets and private runtime preparation are available without PHP errors.

Understand session preservation during module upgrades

Know that routine installer and runtime preparation work preserves the isolated linked-device authentication directory for each account.

Understand deactivation and removal boundaries

Distinguish disabling the CRM module from using the explicit Unlink WhatsApp or Delete account controls; linked-device and compliance history are not silently removed by normal page navigation.