- Home
- Solutions
- Onboarding
- Resolving “Error 400: admin_policy_enforced” Integration Error in Google Workspace
Resolving “Error 400: admin_policy_enforced” Integration Error in Google Workspace
This authorization error occurs if Google Workspace is set to restrict third-party app access. Here's how to fix it:
1. Open the Google Admin Console, and navigate to Security → Access and data control → API controls in the left sidebar. Here, click on Manage third-party app access.
2. Type in “zluri” in the search bar and click App name contains “zluri”.
3. Hover over the Zluri entry and click Change access.
4. Choose whether you wish to change access to the entire organization or to specific org units, and click Next.
5. Set Access to Google data to Trusted. Click Next.
6. Review the changes and click Change access. You can now proceed to connecting Google Workspace to Zluri.
Still need assistance? Please feel free to submit a ticket or contact us directly at [email protected].
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
This authorization error occurs if Google Workspace is set to restrict third-party app access. Here's how to fix it:
1. Open the Google Admin Console, and navigate to Security → Access and data control → API controls in the left sidebar. Here, click on Manage third-party app access.
2. Type in “zluri” in the search bar and click App name contains “zluri”.
3. Hover over the Zluri entry and click Change access.
4. Choose whether you wish to change access to the entire organization or to specific org units, and click Next.
5. Set Access to Google data to Trusted. Click Next.
6. Review the changes and click Change access. You can now proceed to connecting Google Workspace to Zluri.
Still need assistance? Please feel free to submit a ticket or contact us directly at [email protected].
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article