AdminSecurity and governance

Review audit and communication history

To review audit and communication history, start with a signed-in account and a documented reason for the security or governance task. In Admin, filter audit events, search by actor or record, open event detail, and review email history. Use the least access needed, verify the subject and scope, and keep secrets and personal data out of notes and support evidence.

Before you start

A signed-in account and a documented reason for the security or governance task
Verify actor, scope, time, and requested access before making or approving a change

Review audit events

Open /audit and set Business Account, branch, time, actor, action, record, and status filters as needed.
Open the exact event and preserve its reference and timestamp; audit history is read-only.

Review communication history

Open Settings with the Audit section selected and choose the email, WhatsApp, or branch history view.
Apply the intended scope and retain the matching event evidence without inferring data outside it.

Expected result

Audit filters return matching read-only events with actor, action, scope, record, and time evidence. Email, WhatsApp, and branch views remain separate, and opening an event does not change the underlying record.

Permissions

Audit History requires audit.read; communication-history settings routes require settings.read. All views remain Business Account and branch scoped.

Troubleshooting

An expected audit event is missing.

Align Business Account, branch, time range, actor, action, record, channel, and status filters. Check the relevant email, WhatsApp, or branch history view separately before escalating.

An audit event lacks enough detail to investigate.

Preserve the event reference, timestamp, actor, action, and scope exactly as shown. Do not edit source data to recreate evidence; send Support the safe event metadata and missing field.

Set up multi-factor authentication
Enroll the signed-in user’s trusted authenticator without exposing the QR secret or one-time code.Manage personal privacy data
Request the signed-in person’s data export or account deletion once and track the returned status.Review access approval requests
Review one access request and approve only the justified scope or reject it with a recorded reason.