Understand private browser fallback
Know that the installer can prepare a module-owned browser runtime when a suitable system browser is unavailable.
Exact navigationAdmin Area → WhatsApp → Connections
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
Know that the installer can prepare a module-owned browser runtime when a suitable system browser is unavailable. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Exact step-by-step process
- Open Admin Area → WhatsApp → Connections.
- Locate the account, conversation, setting, session or evidence relevant to “Understand private browser fallback”.
- 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
Connector runtimeprivate and loopback-only
Recommended Node.js20.11 or newer
Preparationmanaged from the CRM interface
Session directoryisolated per account
Code-backed validations and workflow rules
- Normal administrators are not asked for SSH, Node.js, ports, URLs, tokens or system services.
- Runtime operations are constrained to module-managed paths and loopback connector endpoints.
- Preparation, repair and build upgrade preserve the retained WhatsApp session unless Unlink or Delete is explicitly confirmed.
- Know that the installer can prepare a module-owned browser runtime when a suitable system browser is unavailable.
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.