CalendoxCalendox Docs
Security & Privacy

OAuth Permissions

The complete list of OAuth scopes Calendox requests from Google, Microsoft, and Zoom, why each one is needed, and how to revoke access at any time.

Calendox uses OAuth 2.0 to connect to Google Calendar, Microsoft Outlook, and Zoom. Below is the complete list of permissions requested for each provider, the reason each scope is required, and how to revoke access at any time.

Google Calendar

Connecting a Google account requests these scopes:

ScopePurpose
openid, userinfo.email, userinfo.profileIdentify your Google account and display your name/email in Calendox
calendar.readonlyRead your calendar list and event details for display and sync
calendar.calendarlistList the calendars in your Google account so you can choose which ones to import
calendar.eventsCreate, update, and delete events in your connected calendars

If you enable Google Meet as a meeting provider (Settings → App → Meeting Apps), Calendox additionally requests meetings.space.created to generate Meet links for your events.

Calendox does not request access to Google Drive, Gmail, Contacts, or any other Google service.

Microsoft (Outlook / Microsoft 365)

Connecting a Microsoft account requests these Microsoft Graph scopes:

ScopePurpose
openid, profile, emailIdentify your Microsoft account and display your name/email in Calendox
offline_accessObtain a refresh token so Calendox can renew access without requiring you to sign in again
User.ReadRead your Microsoft account profile for display
Calendars.ReadWriteRead events from and write events to your Outlook calendars

If you enable Microsoft Teams as a meeting provider (Settings → App → Meeting Apps), Calendox requests a separate authorization with openid, profile, email, offline_access, User.Read, and OnlineMeetings.ReadWrite to create Teams meetings for your events.

Enterprise accounts connect at the Microsoft Entra (Azure AD) tenant level rather than per-user. A tenant administrator grants admin consent for:

ScopePurpose
Calendars.ReadWriteRead and write events across the tenant's connected mailboxes
User.Read.AllList users in the tenant so the admin can map and import their calendars

See Enterprise accounts for the tenant connection flow.

Calendox does not request access to your email, files, contacts, or any other Microsoft service beyond calendars, online meetings, and (for enterprise tenant admin consent) the organization's user directory.

Zoom

Calendox requests the following Zoom OAuth scopes:

ScopePurpose
meeting:write:meetingCreate Zoom meetings when you add a Zoom link to a calendar event
meeting:read:meetingRead meeting details to display the join URL in the event
meeting:delete:meetingRemove the Zoom meeting if you delete the calendar event it was attached to
user:read:userRead your Zoom user ID to associate meetings with your account

Calendox does not access Zoom recordings, chat messages, webinars, or any other Zoom data.

Bookings

Booking pages use the same calendar permissions listed above — no additional OAuth scopes are requested for Bookings. Availability is computed by reading free/busy information from your connected calendars, and each confirmed booking is created as an event on the destination calendar you choose, using the read and write access already granted.

Token storage

OAuth access tokens and refresh tokens are stored server-side only in Calendox's database and are never included in logs or exposed to the browser. Tokens are used only to perform the operations listed above. See Data Security for more details.

Revoking access

You can revoke Calendox's access to any provider at any time:

Revoking access from the provider side also disconnects the integration in Calendox.

Next steps