Audit Trail, verification sessions and compliance evidence

Understand audit-event deduplication

Repeated connector or workflow evidence with the same identity is prevented from creating misleading duplicates. 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.

Audience: Administrators, compliance officers and authorised auditorsPermission: Administrator or Audit Trail capabilityModule v1.0.0 · 2026.07.30-r20.5

Jump to steps

Where to goAdmin Area → WhatsApp → Audit Trail

Before you start

Verify 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 you’ll accomplish

Repeated connector or workflow evidence with the same identity is prevented from creating misleading duplicates. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

Go to Admin Area → WhatsApp → Audit Trail.
Find the account, conversation, setting, session or evidence relevant to “Understand audit-event deduplication”.
Check 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.
Verify the expected state in the related Inbox, Connections, customer history, native CRM record or Audit Trail.

Fields and options to review

AccountAll or one accessible account

StaffAll or one staff member

Action containsAction contains

General audit rowsup to 500

Verification sessionsup to 250

Rules the system enforces

Audit visibility is restricted by account access for non-administrators.
Sensitive context keys such as secrets, tokens, passwords, authorisation, QR/base64 and message-body values are redacted.
Raw submitted verification email is represented by a one-way hash in audit context.
Repeated connector or workflow evidence with the same identity is prevented from creating misleading duplicates.

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.

Was this guide useful?Your response is stored only in this browser.