> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool/examples/example-3-searching-using-divisions.md).

# Example 3: Searching using Divisions

The **Division** tab allows you to directly select a division in which to search. Operators can select and search within more than one division at a time. Results returned will include all information from within all selected divisions, including their associated sub-divisions.

This example shows how, using fields within the **General**, **Related To** and **Division** tabs, you can define your search.

1. Click the **General** tab.
2. Click the **Look In** field and select the option "All Items".
3. Click the **Related To** tab.
4. Open the **Operator Group** List Window (Manage - Operator Groups).
5. Select the relevant Operator Group and drag and drop it into the "Related To" window.
6. Click the **Division** tab.

   The **Available Divisions** grid includes all divisions in which the current operator can view any kind of item.
7. Select "Division 1" and "Division 3" from the **Available Divisions** grid, and drag and drop them into the **Selected Divisions** grid.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f15e52596794aabfdffb3f52f120285b4e52a0e5%2Ffind_divisions.png?alt=media)
8. Click the **Start Search** button.

   All items related to the selected Operator Group, in **Division 1** or **Division 3**, or **Division 2** or **Division 4** display within the Search window.

   Items in **Division 2** and **Division 4** are included in the search result because they are sub-divisions of the divisions that were selected.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool/examples/example-3-searching-using-divisions.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.
