Security, privacy and operational boundaries

Understand loopback connector protection

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

The private connector is intended for 127.0.0.1 and not for public Internet exposure.

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

Jump to steps

Where to goAdmin Area → WhatsApp → Settings / Access Control / 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 this guide helps you do

The private connector is intended for 127.0.0.1 and not for public Internet exposure. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

Go to Admin Area → WhatsApp → Settings / Access Control / Audit Trail.
Find the account, conversation, setting, session or evidence relevant to “Understand loopback connector protection”.
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

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

Rules and limits

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 private connector is intended for 127.0.0.1 and not for public Internet exposure.

Check 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.