Powers Zoom meetings and webinars for Juno events, attendance tracking, and optional recording import.
Why Juno integrates with Zoom
Juno integrates with Zoom using OAuth 2.0 (user-authorized). A user with a Zoom account explicitly grants Juno access through Zoom’s standard consent screen. Access is per-user and per-tenant, and can be revoked at any time from either Juno or Zoom.- Meeting and webinar lifecycle — organizers connect their Zoom account so Juno can create, update, and cancel the Zoom meeting or webinar for an event session.
- Attendance — after a session ends, Juno reads the participant list to mark attendance automatically.
- Recordings (on demand only) — organizers can import a session’s cloud recording into Juno as learning content.
Permissions we request
Juno requests the granular scopes below. Each maps to a single Zoom operation the event features require — nothing broader. Juno’s app is published on the Zoom Marketplace, where Zoom reviews and displays the full scope list on the consent screen.Not requested: Juno does not request scopes for chat, contacts, account-wide administration, phone, or any data unrelated to the event being managed.
What we do with the access
- Meeting / webinar lifecycle — when an event is created, updated, or deleted in Juno, we create, update, or delete the corresponding Zoom meeting or webinar (topic, start time, duration, time zone, agenda, and alternative hosts).
- Attendance sync — after an event ends, a scheduled job reads the participant list and records, per attendee, whether they attended and for how long. Participants are matched by email to users in the same Juno tenant.
- Recording retrieval (on demand only) — when an organizer explicitly requests it, Juno retrieves the completed recording for a specific event. We do not pull recordings automatically or in bulk. Juno checks the granted scopes before every recording download and prompts the organizer to reconnect if the scope is missing.
Data we store
We do not store Zoom account passwords. Tokens are the only credentials held, and they are encrypted at rest.
Security and storage
- Encryption at rest — access and refresh tokens are encrypted at rest using a dedicated server-side encryption key.
- No frontend exposure — tokens are used only server-side; they are never sent to the browser or included in client responses.
- Short-lived access tokens — access tokens are short-lived and refreshed server-side before they expire.
- Scope enforcement — before sensitive operations (attendance sync, recording retrieval), Juno verifies the required permission is present and skips gracefully if it is not.