Pixelogy for Zoom Meetings

Pixelogy for Zoom Meetings is installed by an authorized user on a Zoom account that wants to use Pixelogy Control to drive a render node into Zoom meetings. The integration is intended for live production, signage, venue display, and customer-controlled meeting display workflows.

You need an active Zoom account that can authorize third-party apps. If your Zoom account is managed by a workspace administrator, you may need to ask the administrator to pre-approve Pixelogy for Zoom Meetings before you can install it.

You also need access to a Pixelogy Control deployment. Pixelogy Control runs on the customer's own infrastructure or on a hosted Pixelogy environment. Your Pixelogy administrator gives you the Pixelogy Control URL.

Open the Pixelogy for Zoom Meetings listing on the Zoom App Marketplace and click Add. Review the requested scopes and approve. The requested scopes are user:read:user, meeting:write:meeting, and user:read:token, which are described in the Usage section below.

If your Zoom workspace requires administrator pre-approval, you may see a notice instead of an Add button. Ask your Zoom administrator to approve Pixelogy for Zoom Meetings for your workspace, then return to the listing and install.

Open Pixelogy Control in your browser and sign in with your Pixelogy operator credentials. Open the Zoom view from the main navigation.

If the Zoom view shows a Log in button, click it. Pixelogy Control redirects your browser to Zoom. Sign in with the Zoom account you want to connect and approve the scopes. Zoom redirects back to Pixelogy Control and the Zoom view displays your connected account email and display name.

If you see a setup form instead of a Log in button, your Pixelogy administrator has not yet entered the Zoom OAuth client credentials in Pixelogy Control. Provide the redirect URL shown by Pixelogy Control to your administrator and ask them to complete the one-time OAuth client configuration. The redirect URL is the same URL you registered with the Pixelogy listing on the Zoom App Marketplace.

If installation fails on the Zoom Marketplace listing, confirm your Zoom workspace does not require administrator pre-approval. Try again with the original installer account.

If the OAuth redirect returns to Pixelogy Control with an error state, confirm that pop-up windows are not blocked, refresh the Zoom view, and sign in to Pixelogy Control again before retrying. Make sure the redirect URL configured on the Zoom listing matches the redirect URL displayed by Pixelogy Control.

If you cannot reach Pixelogy Control after the redirect, confirm that your Pixelogy Control URL is correct and that your network can reach it. On-prem deployments are normally reachable only on the customer's network.

Additional help is available at https://www.pixelogy.tech/support.

Use case: link a Zoom user account to a specific Pixelogy Control deployment so operators can request meeting workflows.

Prerequisites: an active Zoom account, Pixelogy Control reachable from the operator browser, and a Pixelogy administrator who has registered the Pixelogy listing's Zoom OAuth client ID and secret with Pixelogy Control.

Behavior: click Log in in the Zoom view, sign in to Zoom, approve the requested scopes, and return to Pixelogy Control. Pixelogy Control stores only the access and refresh tokens required to maintain the authorized connection. The connected account email and display name are shown in the Zoom view.

Scope used: user:read:user lets Pixelogy fetch the connected account email, display name, and Zoom user ID for display in the Zoom account panel.

Use case: an operator wants to start a new Zoom meeting that a Pixelogy render node will join as a visible participant.

Prerequisites: a connected Zoom account with permission to create meetings, at least one online Pixelogy render node, and a display name configured for the node.

Behavior: select a render node, optionally set the display name, and click Quick Meeting. Pixelogy creates a Zoom meeting on the authorized account, shows the meeting ID and passcode, and offers a Start Host link. The render node is requested to join the meeting as a visible participant using the configured display name.

Scope used: meeting:write:meeting lets Pixelogy create a meeting on the authorized account via POST /users/{userId}/meetings.

Use case: a render node should join a meeting that was scheduled or created outside of Pixelogy.

Prerequisites: an online render node, the meeting ID or full Zoom join URL, the passcode if required, and meeting host or cohost permissions to admit the node when the meeting waiting room is active.

Behavior: paste the meeting ID or URL, enter the passcode if needed, set the node display name, and click Join. Pixelogy asks the selected node to join the meeting. The node appears in the participant list as a normal visible participant.

Scope used: user:read:token is used only when the operator needs a Zoom user token for a Meeting SDK join on behalf of the authorized account. Meeting access, recording, and raw media availability remain controlled by Zoom host and meeting settings.

Use case: route the live video of a specific Zoom participant to a managed display surface on a Pixelogy render node.

Prerequisites: the render node has joined a meeting, the meeting host has allowed video for the selected participant, and the operator has access to the project editor.

Behavior: in the Zoom view, Pixelogy lists meeting participants as cards. Click a card to preview metadata, or drag the card onto the editor canvas. Pixelogy creates a surface whose source is zoom://meetingId/participantId. Save and push the project to display the participant on the configured outputs. Pixelogy renders meeting video only while host and meeting settings allow it.

Use case: a render node needs host or cohost capabilities in a meeting, for example to access raw participant video or to enable local recording for an authorized workflow.

Prerequisites: a connected Zoom account, the node already joined to the meeting, and the meeting host willing to grant the requested role.

Behavior: click Host or Cohost. Pixelogy asks Zoom to grant the role to the render node participant. The meeting host may need to approve the request from the Zoom meeting controls. Host and cohost behavior, including any local recording, is governed by Zoom meeting settings and host approval.

Use case: an operator wants the freshest view of meeting participants after roles change or new participants join.

Prerequisites: a render node currently joined to a meeting.

Behavior: click Refresh in the Zoom view. Pixelogy reloads the node and participant status panels. Refresh is also used to reload the connected Zoom account state.

Use case: the render node should exit a meeting it joined through Pixelogy.

Prerequisites: a render node currently joined to a meeting.

Behavior: click Leave. Pixelogy asks the selected render node to leave the meeting. Pixelogy clears the participant cards for that node after the leave request completes.

Use case: a different Zoom account should be connected to Pixelogy Control, or the integration should no longer be authorized.

Prerequisites: an operator with Pixelogy Control access.

Behavior: click Switch to start a new OAuth authorization flow, or click Log out to disconnect the saved Zoom OAuth account from Pixelogy Control. Log out removes the stored OAuth tokens. To fully de-authorize the app from your Zoom account, also remove the integration from the Zoom App Marketplace as described in the Removing The App section below.

Used after authorization to call GET /users/me on Zoom. Pixelogy displays the connected Zoom account email, display name, and user ID in the Zoom account panel so operators can confirm which account is connected.

Used when an operator clicks Quick Meeting. Pixelogy creates a Zoom meeting on the authorized account by calling POST /users/{userId}/meetings.

Used only when Pixelogy needs a Zoom user token for a Meeting SDK join associated with the authorized account. This supports visible render-node meeting participation. It does not bypass Zoom meeting host controls. Meeting access, recording, and raw media availability remain controlled by Zoom meeting settings and host or cohost permissions.

Open the Zoom view in Pixelogy Control and click Log out. Pixelogy removes the stored OAuth access and refresh tokens for that connected account from Pixelogy Control.

Render nodes do not store long-lived Zoom OAuth refresh tokens. Any node sessions that were using the connected account stop using Pixelogy-issued meeting workflows after the disconnect.

Open https://marketplace.zoom.us/user/installed in your browser. Find Pixelogy for Zoom Meetings in the list and click Remove. Approve the removal.

Removing the app from the Zoom App Marketplace revokes the OAuth authorization at the Zoom side. Future Pixelogy requests using the previous tokens will fail and the operator will need to repeat the Add steps to use the integration again.

Pixelogy deletes the stored OAuth access and refresh tokens for the disconnected account from the Pixelogy Control instance where Log out was clicked. If the app is removed from the Zoom App Marketplace without first clicking Log out in Pixelogy Control, the Pixelogy Control instance deletes the now-invalid tokens during its next scheduled refresh, and in all cases within 24 hours.

Operational metadata such as meeting IDs, join requests, status changes, and audit log entries that were processed for the requested workflows is retained per the customer's logging policy on the Pixelogy Control deployment. Pixelogy does not retain Zoom meeting audio or video by default. If a meeting host enabled local recording or recording was generated, that media is controlled by the meeting host and Zoom account settings, not by Pixelogy.

Pixelogy does not sell Zoom user data, use it for advertising, or use it to train machine learning models.

After removal, the disconnected Zoom account can no longer be used through Pixelogy to create Quick Meetings, request host or cohost roles, or join meetings via Pixelogy on that account's behalf.

Any meeting that the render node is currently in continues until the node leaves or the meeting ends. The render node continues to honor Zoom host controls. To stop the node from rendering meeting video immediately, click Leave in the Zoom view before removing the app.

To use Pixelogy for Zoom Meetings again, repeat the Adding The App steps with the same or a different Zoom account.