How to publish the OAuth consent screen in Google Cloud
Open Google Auth Platform, then Audience, and under Publishing status click Publish app, then Confirm. The status changes from Testing to In production, and anyone with a Google account can sign in, not only your test users.
This is for a developer whose Sign in with Google works for them but shows other people Access blocked, or stops once the test user list is full. A new app starts in Testing, where only listed test users can sign in and their sign in can expire after a week. Publishing moves it to In production. If you ask only for name, email and profile, there is usually no review.
Before you start
You need Owner or Editor on the Google Cloud project. The Google Auth Platform branding (app name, support email) must already be set up.
- Time
- About 2 minutes if you only use basic scopes
- Account
- Not walked yet
| Role | What it can do here |
|---|---|
| Owner or Editor | Can change the publishing status and edit test users. |
| Test user | While the app is in Testing, only these Google accounts can sign in. |
-
1
Open Google Auth Platform
In the Google Cloud console, pick your project and open Google Auth Platform from the menu or the search bar.
You should see: The Google Auth Platform overview with Branding, Audience, Clients and Data access in the left menu.
-
2
Check your scopes
Click Data access and look at the scopes listed. If you only see openid, email and profile (or userinfo.email and userinfo.profile), publishing should not need a review.
You should see: A list of the scopes your app requests, grouped as non-sensitive, sensitive and restricted.
-
3
Open Audience
Click Audience in the left menu.
You should see: A Publishing status section showing Testing, a User type, and a Test users list.
-
4
Click Publish app
Under Publishing status, click Publish app.
You should see: A dialog called Push to production? explaining that the app will be available to any user with a Google account.
-
5
Confirm
Click Confirm in the dialog.
You should see: Publishing status reads In production.
-
6
Test with an account that was not a test user
Open your app in a private window and sign in with a Google account that was never on the test user list.
You should see: Google's consent screen with your app's name, not Access blocked.
If it does not work
Publish app opens a list of things to fix, or asks you to prepare for verification. You requested a sensitive or restricted scope. Remove scopes you do not need on Data access, or submit the app for verification and keep testers on the test user list meanwhile.
You cannot add another test user. The Testing limit is 100 users and removed users still count. Publish the app instead of adding more testers.
People see a Google hasn't verified this app warning after publishing. The app is live but its branding is not verified. Users can continue through Advanced. To remove the warning, verify your domain and submit branding for verification on the Branding page.
The Publish app button is missing. The user type is Internal, which is limited to your Google Workspace and has no Testing stage. Switch to External on the Audience page if people outside your organisation need to sign in.
Questions
What does Access blocked: app has not completed the Google verification process mean?
The app is in Testing and the person signing in is not on the test user list. Add them as a test user, or publish the app.
Is there a limit on test users?
Yes, an app in Testing can have up to 100 test users, and a removed user still counts toward that limit. Publishing removes the need for the list.
Will publishing trigger Google's verification review?
Only if you request sensitive or restricted scopes, such as Gmail or Drive data. With openid, email and profile only, the app goes to In production without a review, although Google may still show an unverified notice until branding is verified.
Why do my test users get signed out after a week?
Refresh tokens issued to an External app in Testing expire after 7 days. Publishing to In production stops that.
Can I go back to Testing?
Yes. The Audience page offers Back to testing while the app is In production.
How we checked
Verified 11 Oct 2026 against the live interface on not walked yet.
Related guides
Ready to do it?
Run these 6 steps on your own Google Cloud page. Each step shows in a panel on the page, Next when you are ready.