Scopes

Users must authorize add-ons and other applications that access their data or act on their behalf. When a user runs an add-on for the first time, the add-on UI presents an authorization prompt to start the authorization flow.

During this flow, the prompt tells the user what the application wants permission to do. For example, an add-on might want permission to read a user's email message or create events in their calendar. The add-on's script project defines these individual permissions as OAuth scopes .

You declare scopes in your manifest using URL strings. During the authorization flow, Apps Script presents a human-readable description of the scope to the user. For example, your Google Workspace add-on might use the "Read current message" scope, which is written in your manifest as https://www.googleapis.com/auth/gmail.addons.current.message.readonly . During the authorization flow, an add-on with this scope asks the user to allow the add-on to: View your email messages when the add-on is running.

Viewing scopes

You can see the scopes your script project currently requires by doing the following:

1. Open the script project.
2. At the left, click Overview info_outline .
3. View the scopes under "Project OAuth Scopes."

You can also view the script project's current scopes in the project manifest, under the oauthScopes field, but only if you have set those scopes explicitly .

Setting explicit scopes

Apps Script automatically determines what scopes a script needs by scanning its code for function calls that require them. For most scripts this is sufficient and saves you time, but for published add-ons you should exercise more direct control of the scopes.

For example, Apps Script might give an add-on script project the very permissive scope https://mail.google.com by default. When a user authorizes a script project with this scope, the project is granted full access to the user's Gmail account. For published add-ons, you mustreplace this scope with a more limited set that cover the add-ons's needs and no more.

You can explicitly set the scopes your script project uses by editing its manifest file. The manifest field oauthScopes is an array of all scopes used by the add-on. To set your project's scopes, do the following:

1. View the scopes your add-on currently uses . Determine what changes need to be made, such as using a narrower scope.
2. Open your add-on's manifest file .
3. Locate the top-level field labeled oauthScopes . If it is not present, you can add it.

4. The oauthScopes field specifies an array of strings. To set the scopes your project uses, replace the contents of this array with the scopes you want it to use. For example, for a Google Workspace add-on that extends Gmail you might have the following:

    {
     ...
     "oauthScopes": [
       "https://www.googleapis.com/auth/gmail.addons.current.message.metadata",
       "https://www.googleapis.com/auth/userinfo.email"
     ],
     ...
   } 
   

5. Save the manifest file changes.

OAuth verification

Using certain sensitive OAuth scopes may require that your add-on go through OAuth client verification before you can publish it. For more information, see the following guides:

• OAuth client verification for Apps Script
• Unverified apps
• OAuth verification FAQ
• Google APIs Service: User Data Policy

Restricted scopes

Certain scopes are restricted and subject to additional rules that help protect user data. If you intend to publish a Gmail or Editor add-on that uses one or more restricted scopes, the add-on must comply with all the specified restrictions before it can be published.

Review the full list of restricted scopes before you attempt to publish. If your add-on uses any of them, you must comply with the Additional requirements for specific API scopes prior to publishing.

The Google Workspace Developer Tools extension for Visual Studio Code provides diagnostic information for all scopes including the scope's description and whether it is sensitive or restricted.

Choose scopes for Google Workspace add-ons

The following sections provide scopes that are commonly used for Google Workspace add-ons.

Editor scopes

Below are frequently-used scopes for Google Workspace add-ons that extend Docs, Sheets, and Slides.

Gmail

There are a few scopes that were created specifically for Google Workspace add-ons to help protect user Gmail data. You must add these scopes explicitly to your add-on manifest, along with any others your add-on code requires.

Below are frequently-used scopes for Google Workspace add-ons that extend Gmail; the ones labeled Requiredmust be added to your Google Workspace add-on manifest if your add-on extends Gmail.

Be sure to also replace the very broad https://mail.google.com scope in your add-on with a narrower set of scopes that allow the interactions your add-on needs and no more.

Google Calendar scopes

Below are frequently-used scopes for Google Workspace add-ons that extend Google Calendar.

Google Chat scopes

To call the Chat API, you must authenticate as the Google Chat user or as the Chat app . Each type of authentication requires different scopes, and not all Chat API methods support app authentication.

To learn more about Chat scopes and authentication types, see the Chat API Authentication and authorization overview

The following table shows frequently-used Chat API methods and scopes based on the supported authentication types:

Google Drive scopes

Below are frequently-used scopes for Google Workspace add-ons that extend Google Drive.

Access tokens

To protect user data, the Gmail scopes used in Google Workspace add-ons only grant temporary access to user data. To enable temporary access, you must call the function GmailApp.setCurrentMessageAccessToken(accessToken) using an access token as an argument. You must obtain an access token from an action event object .

The following shows an example of setting an access token to allow access to a message's metadata. The only scope necessary for this example is https://www.googleapis.com/auth/gmail.addons.current.message.metadata .

  function 
  
 readSender 
 ( 
 e 
 ) 
  
 { 
  
 var 
  
 accessToken 
  
 = 
  
 e 
 . 
 gmail 
 . 
 accessToken 
 ; 
  
 var 
  
 messageId 
  
 = 
  
 e 
 . 
 gmail 
 . 
 messageId 
 ; 
  
 // 
  
 The 
  
 following 
  
 function 
  
 enables 
  
 short 
 - 
 lived 
  
 access 
  
 to 
  
 the 
  
 current 
  
 // 
  
 message 
  
 in 
  
 Gmail 
 . 
  
 Access 
  
 to 
  
 other 
  
 Gmail 
  
 messages 
  
 or 
  
 data 
  
 isn 
 't 
  
 // 
  
 permitted 
 . 
  
 GmailApp 
 . 
 setCurrentMessageAccessToken 
 ( 
 accessToken 
 ); 
  
 var 
  
 mailMessage 
  
 = 
  
 GmailApp 
 . 
 getMessageById 
 ( 
 messageId 
 ); 
  
 return 
  
 mailMessage 
 . 
 getFrom 
 (); 
 } 
 

Other Google Workspace scopes

Your add-on may require additional scopes if it uses other Google Workspace or Apps Script services. In most cases you can let Apps Script detect these scopes and update the manifest automatically. When editing your manifest's scope list, do not remove any scopes unless you are replacing them with a more appropriate alternative, such as a narrower scope.

The following table shows a list of scopes that Google Workspace add-ons often use: