Zoom Workplace

What the current integration does

The current Zoom Workplace integration establishes and manages organization-level account authorization. User synchronization and Zoom Phone activity logging are in development and are not currently available production functionality.

Before you connect

• You must be signed in to Navvi One as a tenant administrator with permission to configure integrations.
• You must authorize using a Zoom administrator account that can grant the requested account-level permissions.
• One Zoom account may be reserved per Navvi app namespace. Navvi discovers the Zoom account_id from Zoom's authenticated API response; it does not infer tenancy from email or phone.

Permissions

The approved permissions allow Navvi One to establish the account connection and support the user synchronization and Zoom Phone activity capabilities that are in development. Exact Zoom scope identifiers are shown for transparency.

• Confirm the authorizing Zoom user and account: user:read:user:admin
• List users in the Zoom account for directory synchronization: user:read:list_users:admin
• List Zoom Phone users and their extension details: phone:read:list_users:admin
• List Zoom Phone call-history records: phone:read:list_call_logs:admin
• Read the details of an individual Zoom Phone call record: phone:read:call_log:admin

A Zoom Phone user can be associated with Navvi through their Zoom user or extension identity. An assigned direct number, sometimes called a DID, is optional and is not required.

Connect Zoom Workplace

1. In Navvi One, open Settings → Admin → Integrations → Zoom.
2. Select Connect Zoom.
3. Review the Zoom authorization screen, the Navvi-owned app identity and the requested scope.
4. Sign in to the intended Zoom administrator account and approve access.
5. After Zoom returns you to Navvi One, confirm that the page shows the connection as connected and displays the expected Zoom account identifier.

Navvi uses durable, single-use OAuth state and a Secure, HttpOnly browser nonce. Your Navvi administrator permission is checked again when the authorization callback is processed.

Use the current integration

The current production functionality provides authorization and connection lifecycle management. Administrators can view connection status, the authorized account identifier and granted scopes, reconnect the same account when authorization requires renewal, or disconnect it. User synchronization and Zoom Phone activity logging are still in development.

Reconnect

1. Return to Settings → Admin → Integrations → Zoom.
2. Select Reconnect when Navvi shows that reauthorization is required.
3. Authorize the same Zoom account. A different account cannot replace the existing reservation.
4. Confirm the connection returns to the connected state.

Reconnect replaces the earlier authorization so only the current connection can be used.

Disconnect

1. Open the Zoom integration settings in Navvi One.
2. Select Disconnect and confirm the action.
3. Navvi immediately disables local token use and attempts to revoke the Zoom credentials.
4. If revocation is not confirmed, the connection remains disabled and a tenant administrator can retry Disconnect.

Disconnect removes active credentials after confirmed revocation but preserves the Zoom account reservation and lifecycle history for integrity and audit purposes.

Remove an unused connection

Removal is separate from Disconnect. It is available only to an authorized tenant administrator after the connection is disconnected and Navvi confirms that no Zoom business dependencies exist.

1. Disconnect the integration and confirm its disconnected state.
2. Choose Remove unused connection.
3. Review the dependency check and confirm removal if Navvi reports no dependencies.

The lifecycle removal is transactional and audited. The audit stores a fingerprint rather than raw OAuth credentials. If dependencies exist, keep the disconnected reservation and contact support for guidance.

Current limitations

• Zoom user-directory synchronization is in development and is not currently available production functionality.
• Zoom Phone call-history and Call Element logging are in development; calls are not currently being ingested.
• The requested capability set excludes recordings and audio or video content, recording transcripts, AI call summaries and voicemail content.
• It does not request or process Zoom Meetings data or chat and message content.
• There are no event subscriptions and no Surface, Embed or Connect capability.

Data and security

See the Privacy Policy and Security page for broader Navvi One practices.

Zoom Phone setup for controlled review

For enabled review workspaces, Navvi's embedded Zoom Phone controls use the Zoom desktop application for call audio. Keep the desktop application running and sign both it and the embedded Phone panel into the same licensed Zoom Phone user mapped to your Navvi account. The desktop window can be minimized.

1. Ask your Zoom administrator to enable Automatically Call From 3rd Party Apps for the account.
2. Approve Zoom's desktop call-control consent prompt when you intend to let Navvi make, answer, end or decline calls.
3. Use only a second endpoint that you control for review calls. A working desktop call alone does not verify the embedded controls or the resulting Navvi communication record.

If the panel remains at Calling…, check the signed-in user, the account setting and the desktop consent prompt. If a completed call is missing from Communications, check the Zoom connection status separately: call-history reconciliation depends on current authorization. Reconnect the same reserved account when Navvi requests reauthorization.

See Zoom's Smart Embed guide and third-party call-control instructions. This setup note does not certify that a review workspace has completed production acceptance.

Support

Use the Navvi One support form or email support@navvi.one with your Navvi organization name, the connection state displayed in Navvi and a description of the problem. Never send OAuth codes, access tokens, refresh tokens or other credentials.