IT administrator guide
Allow AdManage.ai in Google Workspace
If someone at your company sees Google's "Access blocked" screen when signing in with Google, your organization needs to approve AdManage.ai in the Google Admin console. This usually takes a few minutes.
Last updated: June 2025
What this error means
Your company uses Google Workspace (managed Google accounts). By default, many organizations block third-party apps until an admin explicitly allows them.
AdManage.ai is not blocked because it is unsafe — Google is enforcing your org's API access control policy. Once you configure access, users can sign in with their work Google account (for example @yourcompany.com).
What you need
- A Google Workspace admin account with Service Settings or Super Admin privileges
- Access to API controls in the Admin console
- The OAuth client ID below (for proactive allowlisting)
Option A — Approve a user access request (fastest)
Step 1 — Ask the user to request access
On the blocked sign-in screen, the employee should click the blue Request access link. That sends the app to your Google Admin pending review queue (usually within a few minutes).
Step 2 — Approve in Google Admin
After they request access, AdManage.ai appears in your pending review queue. Open Apps pending review.
- Sign in at admin.google.com, then open API controls.
- Under App access control, open Apps pending review.
- Find AdManage.ai (or the app from the user's request).
- Click Configure access and select organizational units (whole domain or specific teams).
- For Access to Google data, choose Trusted (recommended) or Limited / Specific scopes per your security policy.
- Save and ask the user to try Sign in with Google again.
Option B — Allowlist AdManage before anyone requests access
Add the app by OAuth client ID so users are not blocked on first sign-in. Open Manage third-party app access.
- Open API controls, then Manage third-party app access.
- Click Add app (or configure a new web application).
- Choose OAuth App Name Or Client ID and paste the client ID below.
- Set access to Trusted (or Limited if your policy requires tighter scopes).
- Apply to your root org unit (
/) or the relevant OUs, then save.
AdManage.ai OAuth client ID
550827967992-96jifucfk5k7leriau1n4sq4elmvs1iv.apps.googleusercontent.comCheck org-wide API settings (optional)
If many apps are blocked, your domain may require explicit allowlisting for all third-party sign-in. Review API access settings under Unconfigured third-party apps.
Allowing only apps that request Sign in with Google basic info is a lighter policy; allowlisting AdManage as Trusted in Option A or B is still the reliable fix for this error.
Which access level to choose
- Trusted — Simplest. Users can sign in and connect integrations (Google Drive, Google Ads, YouTube) when AdManage requests those permissions later.
- Limited— Sign-in plus only "unrestricted" Google data; may block some integration flows until scopes are expanded.
- Specific Google data — Tightest control; you must include the Google sign-in scope and any scopes your team needs for Drive or Ads.
- Block — Do not use if you intend to allow AdManage.
Still not working?
| Symptom | Likely cause | Where to check |
|---|---|---|
| Still access_not_configured | Wrong OU, or a different OAuth client was allowlisted than the one AdManage uses for sign-in. | Configured apps |
| admin_policy_enforced | App is explicitly blocked, not merely unconfigured. | Configured apps |
| Sign-in works, Drive/Ads connect fails | Access level is too restrictive; upgrade to Trusted or add required scopes. | Accessed apps |
| AdManage not in pending review | User did not click Request access; use Option B instead. | Manage third-party apps |
What to tell your team
IT has allowlisted AdManage.ai in Google Workspace. Please sign in again with your work Google account at admanage.ai.
Need help from AdManage?
We cannot change your Google Admin policies on your behalf. If the app does not appear in Apps pending review, send your IT team this page and the OAuth client ID above.
Questions?
or email [email protected].