> For the complete documentation index, see [llms.txt](https://docs.otari.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otari.ai/tools/configure-web-search.md).

# Configure web search

The **Web search** settings let you control how requests from a workspace can access and search the web. You can follow the deployment defaults or customize web access for individual workspaces, including which domains can be accessed and how many results a search can return.

To configure web search for a workspace:

1. Select the workspace in the top-left corner.
2. Go to **Tools** → **Web search**.
3. Under **Web access**, choose whether web search should:
   * **Follow the deployment default**.
   * Be **Allowed** for requests in this workspace.
   * Be **Blocked**, preventing requests from using web search and fetch tools.
4. Set **Max results** to limit the number of results returned by each search.
5. Optionally, add a **Prompt hint** to guide how web search should be used when a request doesn’t provide its own instructions.
6. Use **Allowed domains** to restrict searches and fetched content to specific websites.
7. Use **Blocked domains** to prevent searches and fetches from accessing specific websites.

Workspace settings can make the deployment-level web search policy more restrictive, but they **cannot override it to allow access that has been blocked at the deployment level**.


---

# 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.otari.ai/tools/configure-web-search.md?ask=<question>&goal=<user_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.