Permissions Requested by Webex Add-on for Google Workspace
When you authorize Webex to access your Google account, the add-on requests permissions to access user data. This topic lists the permissions we request, why we need them, and how we handle your data.
User Account Permissions
|
Permission |
Scope |
Data accessed |
What does Webex use it for? |
|---|---|---|---|
|
View your email message metadata when the add-on is running |
Gmail |
Subject line, date and time, invitee list |
When you schedule a Webex meeting in Gmail, the scheduler reads these pieces of information, which are the essential requirements to schedule the meeting. |
|
Run as a Gmail add-on |
Gmail |
— |
Allows the Webex Scheduler to run in a user’s Gmail. |
|
See the events you open in Google Calendar |
Calendar |
Subject line, date and time, invitee list |
When you open an event in Google Calendar, the scheduler reads these pieces of information, which are the essential requirements to schedule the meeting. |
|
Edit the events you open in Google Calendar |
Calendar |
Subject line |
Add Webex conference data info (card UI/property) into current opened calendar event. |
|
Run as a Calendar add-on |
Calendar |
— |
Allows the Webex Scheduler to run in a user’s Google calendar |
|
View and edit events on all your calendars |
Calendar |
Read subject line, date and time, invitee list Edit subject line |
Allows us to support shared calendar scenarios, in the same way as we read from and write to events in a single user's calendar. |
|
View your Calendar settings |
Calendar |
— |
Google OAuth 2.0 requires this scope. See https://developers.google.com/calendar/api/guides/auth. |
|
See info about users on your domain |
Google Workspace Admin |
Webex siteURL in Google User Info |
If you have set a Webex siteURL in Google user info, then we can read this URL and login to this site as the user's default. |
|
Connect to an external service |
Apps Script |
Connect to Webex service |
The Scheduler needs to call the Webex service to request create/update/delete of the associated Webex meeting. |
|
Allow this application to run when you are not present |
Apps Script |
Access Google event object based on Google trigger |
This allows the Scheduler to run when you are not present, in response to a Google trigger, for example to update/delete a meeting in your calendar. See https://developers.google.com/apps-script/guides/triggers/events. |
|
View and manage data associated with the application |
Apps Script |
Application’s cache |
The Scheduler caches some Webex information in Google storage. For example, the Webex site URL and the Webex meeting template. |
|
View your country, language, and timezone |
Apps Script |
User’s current time |
The Scheduler reads your time zone to schedule or update the associated Webex meeting |
|
See your primary Google Account email address |
Other |
User’s Gmail account address |
The Scheduler reads the user’s email address to bind it to their Webex account. |
|
See your personal info, including any personal info you've made publicly available |
Other |
User’s name and preferred language (default) |
The Scheduler reads the user’s public user information, including full name, and the preferred language to use as the user's default. |
Webex Scheduler Architecture Overview
-
Your site administrator uses Site Administration or Control Hub to enable Webex add-on for Google Workspace.
-
Each individual authorizes permissions for the Webex add-on for Google Workspace (if your admin doesn’t authorize) and connects their Google account with their Webex account.
-
Webex subscribes to calendar changes from Google.
-
A user adds a Webex meeting to a Google Calendar event, updates the time or topic, or copies an event to another date and time.
-
The Webex add-on client receives Google Calendar notifications and syncs with Webex.
Google APIs Used by the Webex Scheduler
The tables below provide information on the Google APIs used by the Webex Scheduler.
For most of the cases, the Webex Scheduler uses the Google App Script API. For a few cases, the scheduler uses the Google REST API. Generally, the Google App Script API wraps the associated Google REST API. The Reference URL column points to the Google App Script API where possible but may refer to the Google REST API reference URL if necessary.
|
Google REST API |
What it does |
Reference URL |
|---|---|---|
|
POST https://accounts.google.com/o/oauth2/token |
Get Google Authentication token |
https://developers.google.com/identity/protocols/oauth2/web-server#exchange-authorization-code |
|
GET https://www.googleapis.com/admin/directory/v1/users/{userKey} |
Get the configured user Webex site |
https://developers.google.com/admin-sdk/directory/reference/rest/v1/users/get |
Frequently Asked Questions
- How does Webex secure the integration?
-
Add-on runs on Google cloud platforms server, and no Google data is saved except for Webex meeting info (subject, invitee list) which is stored in Webex backend and deleted after a scheduled meeting ends.
- How do we secure customer data that we “pull” from this integration?
-
We only collect data that we need, and we only store it as long as we need to.
We collect Webex meeting information and store it in the Webex cloud. We delete the meeting information after a given period of time, which you control with your Webex retention policy.
- Do we use a public or private API to connect to the Google service ?
-
Addon runs on Google cloud platform and access to Google’s built-in libraries directly.
