Best practices for submitting Google Workspace addon OAuth verification (Part 2)

Updated: June 6, 2020

9. Youtube video Demonstration

  • The add-on’s logo in the homepage and Oauth consent screen must be identical. If the add-on already published, the add-on’s logo in the Google Workspace marketplace shoule be the same as the hompage and consent screen.
  • Show full URLs of AppScript ID and Google Workspace Marketplace Integration Client.
  • To get OAuth 2.0 Client IDs, choose project, click on Credentials, click on icons next to Client ID to copy Client ID
  • For example, my google cloud project ID is vcard-bulk-barcode, Apps Script ID is, Google Workspace Marketplace Integration Client is In the youtube video, you should show two following URLs: and
  • The video must also show the consent screen when user accepts scopes
  • You neeed to explain the reason why add-on uses each scope. For example, if add-on uses the scope Connect to an external service, you show the paypal payment pricing page
  • You do not need to talk in the video, just show all actions which OAuth Team requires
  • You can host video in any video platforms and share the video public link with OAuth Team. You can host via Youtube, facebook, etc
  • You should use least scopes as much as possible or you could get rejection
  • You can see the example of video demonstration here
    10. Scopes justification
  • Explain all reasons why you use each scope. You can use the scope explaination in the privacy policy page
    11. Include any information that will help Google Team with verification
  • Show Script ID. Go to the app script file, click on File/Project Properties to see Script ID
  • Show Client ID of Google Workspace Marketplace Integration Client and App script ID
    To summarize, OAuth Team will focus on your addon’s name, scopes and you need to explain very clearly about all these things