> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/phishing/setup-errors.md).
# Common setup errors
## Error 400: admin\_policy\_enforced
1. Sign in to the [Google Workspace Admin console](https://admin.google.com).
2. Go to `Security` > `Access and data control` > `API controls` > `Manage Google Services`.
3. In the list of Google Services, find `Google Workspace` and click `Change access`.
4. Select `Unrestricted`, so any application approved by the user can access the service.
## Error 400: access\_not\_configured
The message `Access blocked: your institution's administrator must review Stoïk Protect (Error 400: access_not_configured)` means your organization restricts app authorizations. An administrator must authorize the application manually:
1. On the error page, click `Request Access`.
2. Open the [Pending Access Requests page](https://admin.google.com/u/1/ac/owl/list?tab=pendingReviewApps) in your Google Workspace Admin console.
3. Find the application named `Stoik Phishing Simulation`.
4. Select it and authorize it.
## Blank page
Our phishing tool may consider your IP address a proxy or VPN and ban it. Send your IP address to so we can add it to the allowlist.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stoik.io/human-security/phishing/setup-errors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
