> 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-1-searching-using-general-and-time-details.md).

# Example 1: Searching using General and Time details

This example uses fields within the *General* and *Times* tabs to define the search.

Follow the procedure below to find **all items** that include the name **office** and that were **created after 7am on 01/03/2007**.

1. Click the **General** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-85aa6554118d741b7a093d08d067b11ce1f18bd7%2Fallitems.png?alt=media)
2. Within the Name field, type **office**.
3. Click the **Look in** field and select the option "All Items".
4. Click the **Times** tab.

   The Times tab is used to search for items based on types of events and time criteria.

   **Note:**

   In this example the **Card Activation** and **Card Expiry** radio buttons are disabled. They are only enabled for cardholder searches.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bc6c20084e93c1e8edbbd7c3ac7efad8163e408c%2Ftimestab.png?alt=media)
5. Select the **Created** option, then the **After** option.
6. Type in the **date** 01/03/2007 and the **time** 07:00:00.
7. Click the **Start Search** button.

   The Search window opens and displays all those items that match the set search criteria.


---

# 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-1-searching-using-general-and-time-details.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.
