Loading content

Published April 10, 2026 · Last reviewed April 10, 2026 · EvalSuite Team

Zoom Reviewer Test Plan for EvalSuite

This guide is written for Zoom Marketplace reviewers. It shows the exact EvalSuite flows tied to Zoom authorization, scheduling, cloud-recording transcript ingest, and RTMS live transcript capture.

Reviewer setup requirements

Production Client ID

Use the production Zoom OAuth client during authorization. The consent screen should show the production EvalSuite app, not a staging or development client.

Private reviewer credential package

Actual reviewer usernames, passwords, and any MFA bypass instructions are supplied privately in the submission notes or secure handoff, not on this public page.

RTMS-enabled Zoom host preferred

A licensed Zoom host account with RTMS enabled can validate both the Pro-level recording path and the RTMS live transcript path in one reviewer environment.

What this test plan covers

Zoom asks for a Zoom-specific test plan, not a generic user manual. This guide maps each requested Zoom scope to the concrete EvalSuite behavior a reviewer can verify.

EvalSuite is a user-managed OAuth app. Managers and org admins connect their own Zoom host account inside EvalSuite, then use Zoom-backed scheduling and transcript capture from the EvalSuite product.

  • Reviewer-visible Zoom surfaces in EvalSuite: connect Zoom Host, schedule Zoom-backed 1:1s or Team Syncs, open the Zoom meeting, see live RTMS transcript status in EvalSuite, receive post-meeting coaching from Zoom cloud-recording transcripts, and remove the Zoom host from EvalSuite.
  • Admin-only reviewer surface: configure one workspace fallback host that covers managers who have not connected a personal Zoom host yet.
  • Not shipped: an in-Zoom coach UI. Live coaching and transcript status stay inside EvalSuite.

Before the reviewer starts

The actual reviewer credentials are shared privately in the submission notes. This public guide explains the workflow and the expected account package without exposing secrets.

  • Required seeded data: one EvalSuite workspace with at least one manager, one teammate to schedule against, and if admin fallback should be tested, one org-admin account as well.
  • Required Zoom environment: one Zoom host account with the required plan, cloud recording enabled, and permission to authorize the production EvalSuite app.
  • Authorization must use the production Zoom OAuth client id during the reviewer flow.
  1. Sign in to EvalSuite with the reviewer manager account provided in the submission notes.
  2. Confirm the workspace already contains at least one teammate who can be used for a scheduled 1:1 or Team Sync.
  3. If you are also validating the admin fallback-host flow, keep the separate reviewer admin account and admin-owned Zoom host account ready.

Authorize the Zoom app in production

This is the core OAuth flow tied to the requested Zoom scopes. EvalSuite stores the connected Zoom host identity after Zoom redirects back.

  1. In EvalSuite, open `Settings -> Integrations`.
  2. In the `Zoom Host` card, click `Connect Zoom`.
  3. On the Zoom consent screen, confirm you are seeing the production EvalSuite app and production client id context.
  4. Approve the requested Zoom permissions.
  5. After Zoom redirects back to EvalSuite, confirm the connected account appears under `Personal Zoom Host` with a connected status.

Scope-by-scope validation

The scope names below come from the shipped EvalSuite Zoom code paths plus the official Zoom endpoint documentation for the exact API surfaces used.

Where a scope is tied to RTMS rather than a visible REST endpoint, the current OAuth callback test fixture in the repo confirms the returned token scope string.

`user:read:user`

EvalSuite reads the connected Zoom user identity after OAuth callback so it can bind the correct Zoom host account to the current EvalSuite profile.

  • Reviewer validation: after authorization, the `Personal Zoom Host` card shows the connected Zoom account identity in EvalSuite.

`meeting:write:meeting`

EvalSuite creates new scheduled Zoom meetings for 1:1s and Team Syncs on the effective Zoom host account.

  • Reviewer validation: create a new Zoom-backed 1:1 or Team Sync in EvalSuite and confirm a Zoom join link is saved onto the meeting.

`meeting:update:meeting`

EvalSuite updates an existing Zoom meeting when the manager changes the date, time, or other meeting scheduling details in EvalSuite.

  • Reviewer validation: reschedule an existing Zoom-backed meeting in EvalSuite and confirm the Zoom-backed meeting remains attached with refreshed join details.

`meeting:delete:meeting`

EvalSuite deletes or cleans up Zoom meetings when the meeting is cancelled or when provider cleanup runs after a Zoom host is removed.

  • Reviewer validation: cancel the Zoom-backed meeting or remove the host from EvalSuite and confirm future dependence on that host is removed.

`cloud_recording:read:meeting_transcript`

EvalSuite downloads post-meeting transcript content from Zoom cloud recordings after the signed recording webhook identifies a mapped EvalSuite meeting.

  • Reviewer validation: complete a recorded Zoom meeting with transcript generation enabled, then confirm transcript-derived coaching content appears back in EvalSuite after Zoom finishes processing.

`meeting:read:meeting_transcript`

EvalSuite uses Zoom RTMS transcript data for live in-meeting transcript capture that feeds the active coaching surface in EvalSuite.

  • Reviewer validation: during an active Zoom-backed meeting, keep the EvalSuite live workspace open and confirm transcript snippets begin appearing while the call is in progress.

`meeting:update:participant_rtms_app_status`

EvalSuite uses the RTMS session lifecycle to open and maintain live transcript capture for the mapped meeting. This scope is part of the returned OAuth scope set for the shipped RTMS path.

  • Reviewer validation: with RTMS enabled for the connected host, start the Zoom meeting and confirm EvalSuite transitions from idle or connecting into live RTMS capture status instead of staying disconnected.

End-user functionality exposed in EvalSuite

These are the Zoom-backed flows an end user can actually use in the shipped product.

Manager path: personal Zoom host and scheduled meeting

This is the primary user-facing flow for a manager who wants their own Zoom account to host their own meetings.

  1. Authorize Zoom through `Settings -> Integrations -> Zoom Host`.
  2. Create or edit a 1:1 or Team Sync in EvalSuite.
  3. Choose `Zoom` as the meeting provider and save.
  4. Open the meeting again and confirm the Zoom join link is present.
  5. Click the `Open Zoom` or `Rejoin Zoom` action from the live workspace when ready to join.

Org-admin path: workspace fallback host

This flow is exposed only to org admins. It allows one admin-owned Zoom host to cover managers who do not yet have a personal Zoom host connected.

  1. Sign in as the reviewer admin account.
  2. Open `Settings -> Integrations -> Zoom Host` and connect the admin-owned Zoom host.
  3. Under `Workspace fallback host`, select that admin-owned connection and save it.
  4. Switch back to the reviewer manager account that does not have a personal host connected.
  5. Schedule a Zoom-backed meeting and confirm Zoom is still available through the workspace fallback host.

Post-meeting recording transcript path

This validates the cloud-recording transcript capture flow used for post-meeting coaching inside EvalSuite.

  1. Start the Zoom-backed meeting from EvalSuite.
  2. Record the meeting in Zoom with transcript generation enabled for the host.
  3. Finish the meeting and wait for Zoom cloud recording and transcript processing to complete.
  4. Return to the related EvalSuite meeting record or follow-through surface.
  5. Confirm transcript-backed coaching or transcript snippets are visible in EvalSuite.

Live RTMS transcript path

This validates the live transcript path used during an active call. The live transcript and coaching indicators are visible in EvalSuite, not inside Zoom.

  1. Use a licensed Zoom host account with RTMS enabled.
  2. Open the active Zoom-backed meeting from EvalSuite and join the Zoom meeting.
  3. Keep the EvalSuite live workspace open during the call.
  4. Confirm the Zoom live panel in EvalSuite moves into active RTMS status or starts increasing the saved transcript snippet count.
  5. Confirm the coaching surface updates as transcript data arrives.

Remove the app and validate de-authorization

Zoom requires removal instructions as part of published-app documentation. Reviewers can validate both the EvalSuite-side disconnect and the Zoom Marketplace removal path.

  • Impact of de-authorization: future Zoom-backed scheduling and new Zoom transcript capture stop for that removed host.
  • Historical EvalSuite records already created from earlier meetings remain in EvalSuite until the customer separately requests data deletion through the normal privacy and support path.
  1. In EvalSuite, open `Settings -> Integrations -> Zoom Host`.
  2. Click `Remove from EvalSuite` and confirm the removal.
  3. Verify the removed host no longer shows as the active personal Zoom host in EvalSuite.
  4. If that host was the saved workspace fallback host, verify the workspace fallback no longer points to the removed host.
  5. In Zoom App Marketplace, open `Manage -> Added Apps`, find EvalSuite, and remove it.

Reviewer credentials package

Actual credentials are shared privately with Zoom reviewers. This public page lists what the private handoff includes so the reviewer knows what to expect.

  • One EvalSuite reviewer manager account with access to a seeded workspace.
  • One Zoom host account for that reviewer, preferably with RTMS enabled if live validation is in scope.
  • Cloud recording and transcript generation enabled for the reviewer Zoom host account.
  • At least one seeded teammate in EvalSuite for scheduling a real Zoom-backed 1:1 or Team Sync.
  • When admin fallback validation is requested, one separate EvalSuite org-admin account and one admin-owned Zoom host account.
  • A note in the submission packet that authorization must use the production Zoom client during the reviewer flow.

Sources and verification basis

Need the user-facing setup guide too?

Use the add, use, and remove guide for end-user instructions, then keep this reviewer guide in release notes or submission comments for Zoom functional review.

Open Support · Create workspace