User Problem

When users of a site go to connect to Google Drive, they are required to sign in to Google Drive via an OAuth2.0 flow and grant these permissions to Atlassian:

See, edit, create, and delete all of your Google Drive files
See and download all your Google Drive files
See, edit, create, and delete only the specific Google Drive files you use with this app
See and download contact info automatically saved in your "Other contacts"
See and download your contacts
View and edit events on all your calendars
See, edit, share, and permanently delete all the calendars you can access using Google Calendar
See and download your organization's GSuite directory

These are often too invasive and are blocked by Google Workspace admins. There should be more options to reducing the scope of these permissions, while still allowing users to connect to Google Drive so that they can view Google Drive results in Rovo Search and Chat.

Suggested Solutions

Give users more control over which sets of files that are made available to Atlassian. For example, instead of "See, edit, create, and delete all of your Google Drive files" perhaps it could be for just some of the user's files (like in a folder).

Current Workarounds

Users currently must accept all permissions or not connect to Google Drive with Rovo. Google Workspace admins control whether these permissions are able to be granted by their Google users.

An update will be posted here if users are given more control over which permissions are granting when connecting to Google Drive.