NERP Meetings Marketplace test plan

Use the development environment test.nerp.app/zoom-review/ and your own licensed Zoom test user. The submission provides a funded NERP key containing synthetic project data and no vendor Zoom credentials. The user guide explains installation, usage and removal.

Prepare the project

1. The submission Username field contains Base64 of an encrypted NERP key file. Save it as key-base64.txt and decode to nerp-zoom-review.ntp. On Windows: certutil -decode key-base64.txt nerp-zoom-review.ntp. On macOS/Linux: base64 -d < key-base64.txt > nerp-zoom-review.ntp.
2. Open the review URL, select the decoded file, and enter the submission Password. Open NERP Zoom — Marketplace Review. Demo meeting plan contains synthetic examples.
3. Open Settings → Zoom. The module is installed. A colleague can create a separate NERP key through the normal sign-up flow to test delegated access.

Authorization and meetings

1. Read Data processing notice and choose Connect Zoom account. Authorize your own licensed test user. This update uses the development client and callback https://meetings-dev.nerp.app/zoom_code. Return and select Complete connection. Save NERP changes if prompted, reload, and verify the account, owner role and trial minutes.
2. Create an instant meeting with recording set to When the second participant joins. Use Start as host; Join meeting is for attendees. Admit a second test participant from the waiting room, with consent to record. Check participant join/leave updates and cloud recording. Recording control requires Cloud recording control enabled in Zoom and an eligible plan.
3. End the meeting, refresh history and select Check past participants. Zoom may need time to prepare attendance; retry if needed.
4. Create a planned meeting, edit title and duration, reload and verify. Create a recurring weekly meeting and verify recurrence in Zoom. Cancel the synthetic planned/recurring meetings when finished.

Recordings and analysis

1. Wait for Zoom cloud processing. Open Recordings. The recording.completed webhook retrieves records; Check Zoom recordings also retrieves files for this meeting.
2. Download a recording. The server returns a single-use link without Zoom OAuth credentials. Expand Transcript and check timestamps; expand Analysis and check the summary.
3. For manual processing, disable automatic processing when creating another meeting, then choose Analysis. Retry a failed summary: existing transcript and Speech operation ID are reused. Processing reserves minutes once per recording segment. Each new Zoom identity receives 60 trial minutes; an administrator can credit more.

Organizer and viewer access

1. As owner, open Access and create an Organizer or Viewer invitation. Copy its key privately.
2. In a separate browser session with a second NERP key, open the module, expand Invitation key and enter it. Save/reload. A viewer can read history and results and download recordings, but cannot create/edit/cancel/host meetings or delegate access. An organizer can manage meetings and analysis but cannot delegate access.
3. Revoke the invitation as owner and refresh the second session: access must be rejected.

Removal

1. Choose Connection → Disconnect NERP, reload and verify that connection and invitations no longer work. Original Zoom meetings and recordings remain.
2. Reconnect to test Zoom removal. In Zoom Marketplace, Manage → Added apps → NERP Meetings → Remove. The signed deauthorization callback disables access and clears stored Zoom tokens. Use your own test Zoom user.

Requested scopes

• user:read:user: identify the connected account.
• meeting:write:meeting, meeting:read:meeting, meeting:read:list_meetings: create meetings, obtain fresh host links and reconcile uncertain creation outcomes.
• meeting:update:meeting, meeting:delete:meeting: edit and cancel meetings.
• meeting:update:in_meeting_controls: start cloud recording after the second participant joins.
• meeting:read:participant: join/leave webhook subscriptions.
• meeting:read:list_past_participants: Check past participants on ended meetings.
• cloud_recording:read:list_recording_files, cloud_recording:read:recording: recording.completed, recording retrieval and download.

Profile editing and recording deletion permissions are retained for existing integrations and are not requested by the new NERP authorization flow. The public production callback is https://meetings.nerp.app/zoom_code; development review uses the separate callback above. See user guide, privacy and retention and support.