VibeFix

Guide

admin_policy_enforced: Google says your admin blocked the app

Published by Yosef D., founder of VibeFix

How this guide was made: Written with AI assistance and checked against the sources linked on this page.

Updated

Short answer: Google returns "400 admin_policy_enforced" when your Google Workspace administrator has blocked the app, or has restricted a Google service the app asks for. You cannot change that setting from your account. Ask your administrator to set the app's access in the Admin console under API controls, then sign in again.

Get it fixed: a free check first confirms the problem on your live app, usually in 4 to 10 minutes.

Free. No account needed. It usually takes 4 to 10 minutes.

Want it fixed? For Lovable apps or code on GitHub, our AI agent fixes it in your code for $79 and tests your live app again. If we can't complete your re-check, you get your money back.

What does it mean?

Google's account help page says: "If you get a '400 admin_policy_enforced' error, it means the administrator of your account doesn't allow you to use Sign in with Google. Also, you can't share some of your organization-specific data with the app." It adds that "Sometimes only specific apps are blocked," and says that if you believe you should have access, you should reach out to your Google Workspace administrator.

Google's OAuth 2.0 page describes the same error as: "The Google Account is unable to authorize one or more scopes requested due to the policies of their Google Workspace administrator."

The Admin console assigns each app one of four access levels: Trusted, Limited, Specific Google data, or Blocked. Google's help page says Blocked means the app "can't access any Google service."

Which cause is it?

What you seeCauseFix
Every sign-in to the app fails with this errorThe admin set the app to Blocked for the whole organizationCause 1
Only users in one part of the organization failA policy on an organizational unit (OU) blocks the app for that unitCause 2
The error appears when the app asks for Gmail, Drive, or another serviceThe admin set that Google service to RestrictedCause 3
The error appears when the app requests sensitive or restricted scopesThe admin has not granted access to the app's OAuth client ID for those scopesCause 4

Cause 1: The app is blocked

  1. Find the app's name and its OAuth client ID. Our suggestion: ask the app owner for the client ID. Google's classroom page says to "Check with your development team to understand which OAuth client IDs are being used."
  2. Our suggestion: send the admin the app name and client ID, and ask them to review the app.
  3. The admin opens the Admin console and goes to Menu, then Security, then Access and data control, then API controls.
  4. The admin selects Manage App Access and finds the app in the Configured apps list.
  5. The admin points to the app, selects Change access, and sets it to Trusted or Limited, with the Google data access that the app needs. Google's help page notes that "You must include the Google Sign-in scopes required by the app to allow users to sign in with their Google Account."
  6. Google's help page says changes can take up to 24 hours.

Cause 2: An org-unit policy blocks the app

Google's help page says that if an access policy is applied to an organizational unit and a different policy is then applied to the entire organization, "the first policy remains in effect for the organizational unit." So a Blocked setting on one unit can stay in force after the top-level setting changes.

  1. In API controls, open the app's access details and check which organizational units have a configured access policy.
  2. Find the unit the affected user belongs to. Google's help page says that to block the app for some users, you set Trusted at the top organizational unit and Blocked at a child unit. Reverse that for the affected unit: set it to Trusted or Limited, or remove the Blocked setting there.
  3. Save the change, then ask the user to sign in again after the change takes effect.

Cause 3: A Google service is restricted

Google's OAuth 2.0 page says that "If an admin set any of the services requested in your app's scopes to Restricted (the error is admin_policy_enforced)." Google's help page says that when a service is Restricted, "only internal and third-party apps configured with a Trusted or Specific Google data access setting can access data." An app set to Limited cannot access a restricted service.

  1. In the Admin console, go to Menu, then Security, then Access and data control, then API controls. Select Manage Google Services and check the service the app asks for, such as Gmail or Drive.
  2. Either set the app to Trusted, or to Specific Google data with the scopes it needs, in Manage App Access.
  3. Or set the service to Unrestricted. Google's help page says that when a service is Unrestricted, apps set to Trusted, Limited, or Specific Google data can access the scopes the admin configured.

Google's help page also says that restricting a service stops previously installed apps that are not trusted, and that their tokens are revoked. Check that before you change a service setting.

Cause 4: The OAuth client ID has no access to the scopes

Google's OAuth 2.0 page says that an administrator may restrict "access to all scopes or sensitive and restricted scopes until access is explicitly granted to your OAuth client ID." Google's help page says that "Users might be blocked from activating unverified apps that you don't trust."

  1. The app owner confirms the OAuth client ID the app sends and the scopes it asks for.
  2. The admin adds that client ID under Configure a new app in API controls, with the Google data access the scopes require.
  3. Check that the app's verification status is acceptable for the scopes it asks for. Google's help page says apps requesting sensitive data go through app verification.

How do I check it's fixed?

  1. In the Admin console, open API controls, then Manage App Access. The app should appear in the Configured apps list with a level of Trusted, Limited, or Specific Google data.
  2. Wait up to 24 hours after the change, as Google's help page advises.
  3. Ask the affected user to sign out, sign in to the app again, and grant consent. The error should no longer appear.
  4. If the error still appears after 24 hours, check the organizational unit setting in Cause 2 and the service setting in Cause 3.

FAQ

Can I get around this error myself?

Google's help page tells you to contact your Google Workspace administrator when you believe you should have access.

The error says "Access blocked" and not admin_policy_enforced. Is it the same?

Not necessarily. Google's account help page says that a "400 invalid_request" or "Access blocked" error means the app sent an invalid request, using an authorization method Google does not allow. That is a different error. This guide covers only "400 admin_policy_enforced."

Does this block every Google account at my organization?

Not necessarily. Google's help page says access settings can apply to the entire organization or to specific organizational units, and that sometimes only specific apps are blocked. Check the unit and the app in the Admin console.

How long does the admin change take?

Google's help page says changes can take up to 24 hours.

Can VibeFix fix it for me?

Yes, for apps built in Lovable or any app whose code is on GitHub. The free check confirms the problem on your live app first. If you want it fixed, our AI agent finds the cause, fixes it in your code for $79 and tests your live app again. See pricing.

Related guides

Sources

Last checked: 17 November 2026.

VibeFix is independent. Google Workspace is a trademark of Google LLC.

More guides · Shopify store accessibility · About · Your privacy choices