Skip to main content

Google OAuth Consent Screen

When a user attempts to connect a Google account, Google presents a consent screen. This screen includes a summary of your project, its policies, and the scopes of access your application is requesting.

Configuring your app's OAuth consent screen is crucial as it determines the information displayed to both users and app reviewers, and it registers your app for future.

note

This step is mandatory for users providing Software as a Service (SaaS) through Mixpost Enterprise. However, if you are using Mixpost internally, this step is not required.

  1. In the Google Cloud console, go to Menu > APIs & Services > OAuth consent screen. Go to OAuth consent screen.
  2. Select the user type for your app. If you are providing Software as a Service (SaaS), choose External. Then click Create.
  3. Complete the app registration form, then click Save and Continue.
  4. Add the following scopes, then click Save and Continue:
    • .../auth/youtube and .../auth/youtube.upload — required for YouTube.
    • .../auth/business.manage — required only if you want to use Google My Business.
  5. If you selected External for user type, add test users:
    • Under Test users, click Add users.
    • Enter your email address and any other authorized test users, then click Save and Continue.
  6. Done!
Screenshots:
OAuth consent screen - VerificationOAuth consent screen - Scopes

Scope justification​

When submitting your app for verification, Google requires a justification explaining why each requested scope is needed. You can adapt the example below to match your use case.

Example justification text
Our application allows users to connect their YouTube accounts to manage and publish video content from a unified dashboard.

We use the .../auth/youtube scope to access basic account information required to link the user's channel and enable content management features.

We use the .../auth/youtube.upload scope to allow users to upload and publish videos directly to their YouTube channel from our platform.

These scopes are essential for providing core functionality such as video upload, publishing, and basic channel management. More limited scopes do not provide sufficient permissions to upload or manage video content.

All actions are performed only with the user's explicit consent, and data is used strictly to provide these features.

Demo video​

Google also requires a demo video showing the full OAuth flow in your application. The video must showcase:

  • Connecting a YouTube account through the OAuth consent screen.
  • Publishing a video to the connected YouTube channel from your application.

Upload the video to YouTube (unlisted is fine) and include the link in your verification request.

Conclusion​

Some scopes require additional reviews and requirements because of the level or type of access they grant.

You can also refer to the guide from Google for more detailed instructions.

On this page