Knowledge settings control which documentation tools an agent can use and which released docs those tools can access. Search and file browsing share one scope, configured on the agent.

## Enable the docs tools

Open the agent's **Knowledge** settings and enable either or both tools:

- **Search docs:** finds relevant sections in your documentation.
- **Browse docs as files:** gives the agent a read-only filesystem for exploring and reading whole documents.

Each enabled tool has an execution mode: **Allow** runs it without an approval request; **Ask** pauses for approval before it runs.

With no scope limits enabled, either tool can access all released docs in your organization. Enabling a tool does not limit it to a particular folder or tag.

## Choose the documentation scope

Use **Limit by tags** and **Limit by folders** to narrow the documentation available to both tools:

| Setting                              | Effect                                                                                 |
| ------------------------------------ | -------------------------------------------------------------------------------------- |
| A limit is off                       | That limit does not restrict access. Any other enabled limit still applies.            |
| A limit is on, with nothing selected | No docs match.                                                                         |
| Tags are selected                    | Docs must have at least one selected tag, applied directly or inherited from a folder. |
| Folders are selected                 | Docs must be in a selected folder or one of its subfolders.                            |
| Both limits are on                   | Docs must satisfy both the tag and folder limits.                                      |

For example, selecting a `public` tag and a `Guides` folder makes only docs with that tag inside that folder or its subfolders available. It does not combine all public docs with all Guides docs.

Both tools enforce the same scope.

Save and [publish the agent configuration](/revisions) to make tool and scope changes available to users.

## Read released content

Both tools read the released revision of a document, not its draft. Editing a doc does not change what these tools read until you [release the updated revision](/releasing).

## Continue reading

- [Organizing](/organizing): manage the folders and tags used for scope.
- [Releasing](/releasing): make updated documentation available to agents.