Custom Support Email for Google OAuth Consent Screen (Tutorial)

When registering an app for Google OAuth consent screen, you are required to provide a "User support email"

Often times, this will only show your current (personal) Google Cloud account's email, which can be a problem as you probably don't want this email showing up publicly.

Here's a tutorial on how to add a custom email to your Google OAuth consent screen's "User support email".

Note

This guide will walk you through how to add any email you want to the Google OAuth "user support email" in the consent screen setup, including:

• Any Gmail email address
• Any custom domain email (e.g. "you@example.com") even if not a Gmail email
• Any non-Gmail email address (e.g. "example@yahoo.com")

This will be a step-by-step guide for this post that touches on the solution.

Let's dive in.

Add a new email to IAM & Admin

Go to your Google Cloud dashboard and find or create a new project.

From the sidebar, go to IAM & Admin > IAM:

Here you'll likely see your current Google Cloud account (your personal account). We want to add a new IAM user.

Click "Grant Access" to add a new IAM user (aka "principal") to your Google Cloud project.

Add principal email address

Under the "New principals" heading, enter the email address you want to use for the "User support email".

Then under "Select a role", choose "Owner" as the role for this account.

If you're using a Gmail account, this should have no problems. You can click "Save" and skip ahead.

But any other non-Gmail account, you will see an error:

CopyEmail addresses and domains must be associated with an active Google Account, Google Workspace account, or Cloud Identity account.

(Optional) Fix the non-Google account IAM principal error

To fix this error, we'll need to create a Google account for your email.

You will need to do this if you have a custom domain email (e.g. you@example.com) or any non-Gmail account (e.g. example@yahoo.com).

First, go to Google's SignUpWithoutGmail link.

Fill out the name, birthdate, and gender questions.

Then input your desired user support email into when it prompts to "Use your existing email":

Google will then send you a verification email to verify you have access to this email:

Once verified, you can go back to your IAM & Admin in Google Cloud to finish adding a new principal.

Finish adding IAM principal to Google Cloud

Now when you enter the desired email address to the "New principals" input, you shouldn't receive any errors.

If you still receive an error after creating a Google account for your non-Gmail email, try reloading the page.

Then click "Save".

This will send a verification email to your new email:

Click the link the email to join the Google Cloud project.

Important

Make sure to sign into the newly-added "Owner" account you've just added to your Google Cloud project before continuing

Use the new email for your OAuth consent screen

After signing out and signing into your new Google account, go to "APIs & Services" > "OAuth consent screen"

In the "App information" section, you should now be able to see the newly added email in the "User support email" field.

And that's it! You will be all set.

Wrapping up

Hopefully this short guide has helped you add a custom email address to Google OAuth consent screen's "User support email" field.

It's a small, but annoying issue but luckily one that can resolved. The best part is, you can use any email you want—including non-Gmail email addresses and custom domain emails.