Manage OAuth App Branding - Google Cloud Platform Console Help (original) (raw)
Your OAuth app branding settings controls what users see in the sign-in and consent screens when they are authorizing access to your app. These include information such as your App Name, Logo, Support email and relevant links sharing more information about your app.
Note : In order for your app name and/or logo to be displayed, you must submit your app for verification.
To manage your OAuth app branding settings, navigate to the Branding page of the Google Auth Platform
App Information
App Name
Choose an app name that distinctively represents your business. Do not use names that may be confused with Google's or other organizations' brands or combine Google product names with generic terms like "app" or "mobile." Refer to the Google Brand Resource Center guidelines for naming your app/product for more information.
Examples of unacceptable names:
- YouTube
- Google+ Online
- Google Drive for iOS
- Mobile YouTube app
- Gmail for Android
- Google Photo App
Examples of acceptable names:
- Photo Browser
- Inbox Assistant
- PDF Viewer for Google Drive
- Top YouTube Videos
The app name will be displayed on the OAuth consent screen only if your app has been verified. See the
OAuth App Verification Help Center
page for details on the verification process.
User support email
The User Support Email field requires you to specify an email address that will be displayed to users on the consent screen. This should be an email address that you regularly monitor so that you can answer questions they have about sign-in, authorization, or your app in general. The drop-down selection box will show you the available options for the User Support Email, which must be one of the following:
- The address of a Google Group managed by the currently logged-in user. If you are a Google Workspace user, you can use an existing group or create a new group in your organization before selecting it as the User Support Email.
- The email address of the currently logged-in user, which must be registered as a Google account. To use a non-Gmail address, you must
- log in to the Google API Console with the Google Workspace account which you want to use for the User Support Email, OR
- register an existing non-Gmail address when creating a Google account; make that account a project editor or owner, then log in with the new account so that it appears as a drop-down selection
App Logo
Specifying a logo for your app helps people recognize your app when the sign-in and consent screens are presented to them.
Logo requirements
- Uploaded image should actually represent your app
- Image should not be larger than 1MB
- Supported image formats include JPG, PNG, and BMP.
- Image should be square and 120px by 120px for the best display results.
If your application is external and has the publishing status of production, your app will go through the verification process before your uploaded icon is displayed on the consent screen.
Updating or deleting your App logo
To delete your application logo, click on the REMOVE button in the App logo section of the Branding page.
To change your application logo, click on the Change logo icon in the App logo section of the Branding page page and upload your new logo.
Uploading a new logo will require you to go through the verification process if your application is external and has the publishing status of production.
App Domain
The App Domain allows you to specify your home page, privacy policy, and terms of service links. It is recommended that you provide these links so users can learn more about your application and data practices.
Note : These links are required for all external production apps. You will not be able to submit your app for verification if it is missing these links.
To protect you and your users, the domains used for each of these links and any links in your project must be registered as authorized domains.
Authorized domains
All domains used in your project, whether in the branding page or client configuration pages must be pre-registered here.
To protect you and your users, Google restricts your OAuth 2.0 application to using Authorized Domains. If you have verified the domain with Google, you can use any Top Private Domain as an Authorized Domain.
After you add an Authorized Domain, you can use any of its subdomains or pages, and any other associated country codes.
Add your Authorized Domains before you add your redirect or origin URIs, your homepage URL, your terms of service URL, or your privacy policy URL.
If your app needs to go through verification, please go to the Google Search Console to check if your domains are verified. Learn more about the authorized domain limit.
Developer contact information
To keep you updated on any changes related to your project, Google will send notifications to the email addresses listed here. Ensure that the provided email addresses are current, as critical information about your project will be regularly communicated to these addresses.
Manage App Audience Configuration
Publishing Status
User Type
Was this helpful?
How can we improve it?