Powers room booking for Juno events and Juno-managed calendar invites for sessions.
Why Juno integrates with Google Calendar
- Room booking — admins can attach meeting rooms from your Google Workspace room directory to Juno events, and Juno checks room availability before booking.
- Juno-managed invites — Juno creates and maintains calendar events for sessions (title, time, attendees, location, video link) so learners get standard calendar invites and RSVP tracking.
Permissions we request
Admin consent (one-time, by a Google Workspace admin)
Per-user calendar connection (delegated, each user consents)
Users who sync their own calendar with Juno grant these scopes for their own account only:Juno scheduler (service account with domain-wide delegation)
To create invites on behalf of your organization, Juno uses a Google service account with domain-wide delegation, restricted to a designated scheduling mailbox you choose:The delegation grant is limited in your Google Admin console to the scopes above. Juno does not read the content of personal calendars — only room free/busy and the events Juno creates.
What we do with the data
- Room directory entries are cached so admins can pick rooms inside Juno.
- Room free/busy responses are used at booking time and are not retained.
- Events Juno creates (attendee emails, times, RSVP responses) are stored to keep sessions and attendance in sync.
Security and storage
Admin OAuth tokens are encrypted at rest and used only server-side. The service account key is held in Juno’s secret store and is never exposed to browsers or logs.Revoking access
- In your Google Admin console, remove the app’s access under Security > API controls, and delete the domain-wide delegation grant.
- In Juno, disconnect the calendar integration from the admin integration settings.