Management OS for Zoom — Test Plan.

The test Zoom account must have these features enabled for the test plan to exercise all scopes:

• Zoom Pro or Business plan (Free plans cannot exercise cloud recording or AI Companion scopes)
• Cloud Recording enabled in account settings, with at least one recorded meeting in the past 30 days
• Audio Transcript enabled in cloud recording settings, with at least one transcript generated
• AI Companion enabled with at least one meeting summary generated

If the test account does not have all four prerequisites, the cloud recording and AI Companion test steps will return empty results (not errors) — this is expected behavior, not an integration failure.

1. Open https://app.mgmt-os.ai/sign-in in a clean incognito browser window
2. Sign in using the Management OS test account credentials provided in the Marketplace release notes
3. You will land on the Management OS application home. Verify the workspace name in the top-left shows the test account's workspace

Expected result: Successful sign-in. Application loads with the test workspace context.

1. Navigate to Settings → Integrations
2. Locate the Zoom integration card in the directory
3. Click Connect Zoom
4. Management OS redirects to Zoom's consent screen at zoom.us/oauth/authorize

Expected result: Zoom consent screen renders showing Management OS as the requesting app and listing the 7 required scopes.

On Zoom's consent screen, verify the following 7 scopes are displayed (and only these 7 — no additional scopes should appear):

• meeting:read:list_meetings
• meeting:read:meeting
• cloud_recording:read:list_user_recordings
• cloud_recording:read:recording
• cloud_recording:read:meeting_transcript
• conversation:read:summary
• user:read:user

Sign in to the Zoom test account if not already signed in. Click Allow.

Expected result: Zoom redirects back to app.mgmt-os.ai/settings?zoom=connected. A green success banner appears: "Zoom connected. Your meetings and recordings will appear in the Daily Brief within about 60 seconds."

1. On the Settings page, locate the Zoom integration card under Connected Integrations
2. The connected account label should display the Zoom test user's display name and email

Expected result: Zoom test account's name and email visible in the Management OS Settings UI. This exercises the user:read:user scope by calling Zoom's GET /users/me endpoint to display identity.

1. Navigate to Ask Anything (AMA) in the left sidebar
2. Type the question: "Show me my upcoming Zoom meetings this week."
3. Submit the question and wait for response (typically 3-8 seconds)

Expected result: Management OS returns a structured list of upcoming meetings from the test Zoom account, showing topic, scheduled time, host, and duration. This exercises both meeting:read:list_meetings (to enumerate meetings) and meeting:read:meeting (to read each meeting's detail). If the test account has no upcoming meetings, Management OS returns "No upcoming meetings found" — not an error.

This step exercises three scopes: cloud_recording:read:list_user_recordings, cloud_recording:read:recording, and cloud_recording:read:meeting_transcript.

1. Navigate to Ask Anything
2. Type: "Summarize the most recent recorded Zoom meeting transcript."
3. Submit and wait for response (typically 5-15 seconds — Management OS calls Zoom to list recordings, fetches the most recent one's transcript, and synthesizes a summary via Anthropic Claude)

Expected result: Management OS returns a summary of the most recent recorded meeting's transcript, including meeting title, date, and key conversational themes. If the test account has no recorded meetings with transcripts, Management OS returns "No transcribed recordings found" — not an error.

1. Navigate to Ask Anything
2. Type: "What are the action items from my most recent Zoom meeting with AI Companion?"
3. Submit and wait for response

Expected result: Management OS returns the AI Companion summary content for the most recent meeting that has one, including action items and next steps. This exercises the conversation:read:summary scope. If no AI Companion summaries exist, returns "No AI Companion summaries found" — not an error.

1. Navigate back to Settings → Integrations
2. Locate the Zoom integration in the Connected Integrations list
3. Click Disconnect
4. Confirm the disconnect in the modal that appears

Expected result: Zoom integration immediately removed from the Connected Integrations list. Management OS internally deletes the OAuth access token, refresh token, and stored Zoom user identity from its Supabase database. No further Zoom API calls will be made for this workspace until the integration is reconnected.

To verify on Zoom's side: sign in to marketplace.zoom.us → Manage → Added Apps. Management OS will still appear there because Zoom's OAuth metadata persists until the user explicitly uninstalls. To complete the revocation from Zoom's side: click Remove on the Management OS row.

1. After Step 8 disconnect, return to Settings → Integrations
2. Click Connect Zoom again
3. On Zoom's consent screen, click Cancel or Deny instead of Allow

Expected result: Management OS surfaces a friendly error banner: "You declined consent. Click Try Again when you're ready to grant access." This validates the OAuth error handling path and the user-facing copy mapped to the access_denied error code.

If any test step fails unexpectedly, send the following to support@mgmt-os.ai for fast diagnosis:

• The step number that failed
• The exact error message or unexpected behavior
• The browser URL at the time of failure (especially useful for OAuth callback errors — the URL includes the reason code)
• Browser console output (DevTools → Console tab) if available

For Zoom-side issues (consent screen errors, missing scopes), check the live scope registration at marketplace.zoom.us — Management OS app scopes.

All 7 production scopes exercised by this plan:

1. meeting:read:list_meetings — Step 5
2. meeting:read:meeting — Step 5
3. cloud_recording:read:list_user_recordings — Step 6
4. cloud_recording:read:recording — Step 6
5. cloud_recording:read:meeting_transcript — Step 6
6. conversation:read:summary — Step 7
7. user:read:user — Step 4