Security, privacy and operational boundaries

Understand the no-Business-API boundary

The module does not use WhatsApp Business API, Cloud API, Meta Graph API or public Meta webhooks.

Audience: Administrators, security engineers and data-protection staffPermission: Administrator and security/compliance rolesModule v1.0.0 · 2026.07.30-r20.5

Exact navigationAdmin Area → WhatsApp → Settings / Access Control / Audit Trail

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

The module does not use WhatsApp Business API, Cloud API, Meta Graph API or public Meta webhooks. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Exact step-by-step process

Open Admin Area → WhatsApp → Settings / Access Control / Audit Trail.
Locate the account, conversation, setting, session or evidence relevant to “Understand the no-Business-API boundary”.
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

Encrypted connector tokensEncrypted connector tokens

Loopback-only endpointsLoopback-only endpoints

Isolated per-account sessionsIsolated per-account sessions

CSRF-protected state changesCSRF-protected state changes

Permission-scoped media and historyPermission-scoped media and history

Code-backed validations and workflow rules

The connector uses local linked-device WhatsApp Web and does not turn the CRM into a WhatsApp Business API client.
Normal administrators never need to reveal connector credentials or access authentication directories.
Account access, verified customer ownership and protected download checks are enforced server-side.
The module does not use WhatsApp Business API, Cloud API, Meta Graph API or public Meta webhooks.

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.