Please update the Asana Google Drive integration to use Google’s restricted [u]https://www.googleapis.com/auth/drive.file[/u] OAuth scope instead of the broad [u]https://www.googleapis.com/auth/drive[/u] scope.
This change would allow security conscious enterprise customers to enable the Google Drive integration while maintaining the principle of least privilege.
The Problem
Our organization block applications that request the full [u]https://www.googleapis.com/auth/drive[/u] permission because it grants read and write access to all files in a user’s Google Drive.
Proposed Solution
Update the Google Drive integration to use Google’s more restrictive OAuth scope:
The drive.file scope allows applications to:
- Create files
- Open files that users explicitly select or create through the application
It does not grant access to every file in a user’s Google Drive, making it significantly more acceptable from an enterprise security perspective.
Additional Context
This limitation has previously prevented our organization from enabling the Google Drive integration after a security review. Multiple internal teams have since expressed interest in using this capability, but the current OAuth permissions remain the blocker.
Using the restricted drive.file scope would address the primary security concern while preserving the core functionality of the integration.