January 8, 2025
Granular OAuth consent in Google Apps Script IDE executions
What’s changing
Additional details
- The user, who has granted consent to a subset of the requested OAuth scopes, tries to run a part of the script that was not previously authorized.
- The script is updated in such a way that it requires permission for additional scopes.
- The user revoked access to the script from their Google Account settings.
Getting Started
- Admins: There is no admin control for this feature.
- Developers and end users:
- Granular OAuth consent is only available for scripts that have finished migrating to the V8 runtime. If you would like to utilize granular consent on one of the few remaining Rhino scripts, you can manually migrate to V8 by following these instructions.
- This new consent screen will only be used for new OAuth scope grants. Pre-existing scope grants will not be affected, so no action is required by users on scripts they’ve already authorized.
- The new consent screen will be launched first to the Apps Script IDE (i.e. executing a script directly from Apps Script). The consent screen will launch to the remaining surfaces in the future:
- Google Ads Script
- Macro executions
- Trigger executions
- Web app executions
- API Executions
- Chat apps
- Add-ons
Rollout pace
- Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on January 8, 2025, with expected completion by January 24, 2025
Availability
- Available to all Google Workspace customers and Workspace Individual Subscribers
Resources
- Developer Documentation: Migrating scripts to the V8 runtime
- Developer Documentation: Class ScriptApp