Granular OAuth consent in HTTP Google Workspace add-ons

What’s changingGranular OAuth consent is rolling out over the next few weeks for Google Workspace add-ons built using HTTP endpoints. Granular consent gives users clear choices about the data they share with third-party applications.This update is similar to an update made earlier this year with the introduction of granular OAuth consent in the Google Apps Script IDE: when someone installs or runs an HTTP Workspace add-on that supports granular consent, they will see a redesigned consent screen. Instead of being asked to authorize all requested permissions at once, users can selectively grant access to individual OAuth scopes.For example, Google Workspace add-ons can extend to multiple Workspace apps, but users might only use an add-on for some of the apps it extends. With granular consent, users can choose to grant all permissions to an add-on or grant permissions as needed when they use the add-on in each app.This screenshot shows the new OAuth consent screen, which lets the user provide consent for a subset of the requested OAuth scopes.Additional detailsFollowing is the timeline for developers supporting granular consent in HTTP Google Workspace add-ons:New HTTP Google Workspace add-ons built after May 27, 2025 must support granular consent. Existing add-ons have until December 1, 2025 to add support for granular consent. After December 1, 2025, all HTTP Google Workspace add-ons must support granular consent.After a user grants permission to a Google Workspace add-on that supports granular consent, the add-on might request OAuth consent again in the following cases:The user, who has granted consent to a subset of the requested OAuth scopes, tries to run a part of the add-on that requires scopes that were not previously authorized.The add–on is updated in such a way that it requires permission for additional scopes.The user revoked access to the add-on from their Google Account settings.This update does not apply to the following scenarios, for which granular consent may become available in the future:When an admin initially installs an add-onWhen an admin updates the permissions granted to an add-on from the Admin consoleIf a Google Workspace add-on is built in Apps ScriptGetting StartedAdmins: There are no changes to the admin controls for this feature.Developers: For information about how to add support for granular consent to HTTP Workspace add-ons, refer to the developer documentation.End users: 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 add-ons they’ve already authorized. Rollout paceRapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on May 6, 2025, with expected completion by May 19, 2025AvailabilityAvailable to all Google Workspace customers and Workspace Individual SubscribersResourcesDeveloper documentation: Build a Google Workspace add-on using HTTP endpointsWorkspace Updates Blog: Granular OAuth consent in Google Apps Script IDE executions

May 10, 2025 - 11:47

Granular OAuth consent in HTTP Google Workspace add-ons

What’s changing

Granular OAuth consent is rolling out over the next few weeks for Google Workspace add-ons built using HTTP endpoints. Granular consent gives users clear choices about the data they share with third-party applications.

This update is similar to an update made earlier this year with the introduction of granular OAuth consent in the Google Apps Script IDE: when someone installs or runs an HTTP Workspace add-on that supports granular consent, they will see a redesigned consent screen. Instead of being asked to authorize all requested permissions at once, users can selectively grant access to individual OAuth scopes.

For example, Google Workspace add-ons can extend to multiple Workspace apps, but users might only use an add-on for some of the apps it extends. With granular consent, users can choose to grant all permissions to an add-on or grant permissions as needed when they use the add-on in each app.

This screenshot shows the new OAuth consent screen, which lets the user provide consent for a subset of the requested OAuth scopes.

Additional details

Following is the timeline for developers supporting granular consent in HTTP Google Workspace add-ons:

New HTTP Google Workspace add-ons built after May 27, 2025 must support granular consent.
Existing add-ons have until December 1, 2025 to add support for granular consent.
After December 1, 2025, all HTTP Google Workspace add-ons must support granular consent.

After a user grants permission to a Google Workspace add-on that supports granular consent, the add-on might request OAuth consent again in the following cases:

The user, who has granted consent to a subset of the requested OAuth scopes, tries to run a part of the add-on that requires scopes that were not previously authorized.
The add–on is updated in such a way that it requires permission for additional scopes.
The user revoked access to the add-on from their Google Account settings.

This update does not apply to the following scenarios, for which granular consent may become available in the future:

When an admin initially installs an add-on
When an admin updates the permissions granted to an add-on from the Admin console
If a Google Workspace add-on is built in Apps Script

Getting Started

Admins: There are no changes to the admin controls for this feature.
Developers: For information about how to add support for granular consent to HTTP Workspace add-ons, refer to the developer documentation.
End users: 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 add-ons they’ve already authorized.

Rollout pace

Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on May 6, 2025, with expected completion by May 19, 2025