Cannot Access OAuth Consent Screen or Add Test Users for Gmail API Project

Google Cloud Compute Infrastructure
1

Hello,

I am trying to set up the Gmail API for my Google Cloud project, but I am unable to access the OAuth consent screen setup. When I click “OAuth consent screen” in the APIs & Services sidebar, I am only shown the metrics dashboard and do not see any option to configure the consent screen or add test users.

I have already:

  • Enabled the Gmail API for my project.

  • Created OAuth credentials.

  • Tried different browsers and cleared cache.

But I cannot proceed with the OAuth flow because my app is blocked (“Access blocked: JARVIS Email Integration has not completed the Google verification process”). I do not see any “Configure consent screen” or “Get started” button at the top of the page.

Is there a way to force the consent screen setup to appear, or is there a project/billing setting I am missing? I am not trying to use paid services—just the Gmail API for personal/testing use.

Thank you for your help!

2

Hey,

Hope you’re keeping well.

This behavior indicates that the project is missing an active OAuth consent configuration, which normally appears under APIs & Services > OAuth consent screen. In most cases, the option disappears when you are viewing a Workspace-managed project that does not have permission to configure external apps or when the project was created under a restricted organization policy that disables the OAuth consent configuration UI. Verify that you are working in a standard Cloud project and not under a Workspace-managed project tied to your corporate domain. In the Google Cloud Console, switch to a personal project by using the project selector in the top navigation bar, then navigate again to APIs & Services > OAuth consent screen and select “Configure consent screen.” Choose “External” if you intend to test with non-domain users and add test users in the same view.

If the option remains hidden even in a personal project, confirm that you have the roles roles/editor or roles/oauthconfig.editor on that project. You can grant it using `gcloud projects add-iam-policy-binding PROJECT_ID –member=user:YOUR_EMAIL –role=roles/oauthconfig.editor`. Once permissions are correct, the configuration UI will appear, allowing you to complete the consent setup and unblock the Gmail API OAuth flow.

Thanks and regards,

Taz

3

Hi! Just faced the same issue.

Posting this in case it saves someone time.

My Google OAuth verification kept failing with errors like:

  • homepage does not explain the purpose of your app

  • privacy policy link not found

  • homepage requirements not met

But my site clearly had:

  • working homepage

  • /privacy and /terms pages

  • links visible

  • 200 responses

Turns out the issue was bot protection/security rules blocking Google’s crawler.

Google’s verification system uses bots to automatically check your homepage and privacy policy. If you have any of these enabled:

  • bot protection

  • WAF rules

  • JS challenges

  • CAPTCHA

  • rate limiting

  • “under attack” mode

  • firewall blocks

their crawler can’t load your site, so they think your pages don’t exist.

What fixed it

I temporarily disabled bot/security challenges (or whitelisted Googlebot), then resubmitted verification.

It passed immediately.

TLDR

If verification says your homepage/privacy policy is missing but it’s clearly there:
make sure Google’s bots can access your site without challenges.

It’s usually a security/firewall/bot protection issue, not your HTML.

4

The issue occurs because your project lacks the OAuth consent setup or is restricted by organization policies. Switch to a personal Cloud project, then go to APIs & Services > OAuth consent screen, choose External, and add test users. Ensure you have the role roles/oauthconfig.editor; once done, the consent screen will appear and the Gmail API OAuth flow will work.

5

Ohhh ok ok so it was a bug so i can go back and get what i need now have they fixed the bug?