title: Branding the "Authorize access" button for a unverified Gmail add-on app?
body: <p>So, I am trying to get my Gmail add-on approved by Google and I am struggling with one last thing.</p>
  
  <p>My app use "sensitive" scopes (such as <code>gmail.addons.current.message.readonly</code>) and therefore the user needs to authorize that my app is allowed to do that. For apps that haven't yet been approved by Google, the user is prompted with an "Authorize access" button (see <a href="https://i.stack.imgur.com/MweLM.png" rel="nofollow noreferrer">image</a> and this link <a href="https://developers.google.com/gsuite/add-ons/how-tos/authorizing-addons#authorizing_unpublished_g_suite_add-ons" rel="nofollow noreferrer">https://developers.google.com/gsuite/add-ons/how-tos/authorizing-addons#authorizing_unpublished_g_suite_add-ons</a>).</p>
  
  <p>Now, I have received feedback from the OAuth Verification Dev Team at Google that I have to change this button to the Google brand guidelines. My problem with this is that the screen that needs to be changed is a default Gmail Authorization screen (for unverified apps only) and I dont know how to change that...</p>
  
  <p>Does anyone have any idea how to proceed? I have emailed the OAuth devs mutiple times, but they dont provide me with any pointers, only threats that my app will be rejected if I don't comply.</p>
  
  <p>UPDATE: The full response from the Google team below:</p>
  
  <p><em>Thank you for your response.</em> </p>
  
  <p><em>Please note, that since the 'Authorize Access' button initiates the OAuth Sign-in process it is subject to comply with the <a href="https://developers.google.com/identity/branding-guidelines#top_of_page" rel="nofollow noreferrer">Google sign-in branding guidelines</a>.</em> </p>
  
  <ul>
  <li><em>You may refer to Figure 2: Unverified app authorization flow on our
  <a href="https://developers.google.com/apps-script/guides/client-verification" rel="nofollow noreferrer">OAuth Client Verification page</a>, which showcases the full OAuth
  Sign-in process.</em>  </li>
  </ul>
  
  <p><strong><em>Google Sign-in Branding</em></strong></p>
  
  <p><em>In order to proceed with the <a href="https://support.google.com/cloud/answer/9110914#verification-types" rel="nofollow noreferrer">sensitive scope verification</a> for the project: xxx-xxx, please update the previously flagged Google sign-in button so that it complies with the Google sign-in branding guidelines.</em>   </p>
  
  <p><em>Please reply to this email once you have made the appropriate updates to your site and/or your OAuth Consent Screen so that we may continue with the verification process.</em>  </p>
  
  <ul>
  <li><strong><em>Note:</strong> Failure to satisfy/provide the preceding information might
  result in a rejection of your request. To avoid this outcome, update
  the applicable information in your request to meet our requirements.</em></li>
  </ul>