> 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-4-advanced.md).

# Example 4: Advanced

The following four examples show how, using fields within the Advanced tab, you can define your search.

**Note:**

The information displayed on the Advanced tab will vary depending on the item you select within the "Look in" field on the General tab.

For example, if within the General tab, you select "Cardholder", you are prompted to enter criteria related to cardholders. This same information would not be displayed if you selected "HBUS I/O".

<details>

<summary>Example 4-A</summary>

You may want to check which [*HBUS I/O Interfaces*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#hbus-i-o-interface) within the system have not yet been configured.

1. Click the **General** tab.
2. Within the **Look in** field select "HBUS I/O".
3. Click the **Advanced** tab.
4. **Check the box** to exclude those items with a valid address.

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

   Those HBUS I/O Interfaces with an invalid address display within the Search window.

</details>

<details>

<summary>Example 4-B</summary>

You may want to find out which Cardholders issued with card numbers between 10 and 50 are Contractors.

**Note:**

This example would only be possible if you had a card type for "Contractor Card" set up.

1. Click the **General** tab.
2. Within the **Look in** field select "Cardholder".
3. Click the **Advanced** tab.
4. Within the **Range** field, type in the range of card numbers 10 to 50.

   **Notes:**

   * "Card Number" and "Card Range" cannot both be defined in your search. When you start to enter details in one of these fields, the other becomes disabled.
   * The **Number** field accepts wildcard characters, (e.g. %), if there is no **Type** selected or the card number format is NOT decimal.
5. From the **Type** drop-down list, select **Contractor Card**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8423bf3fee7f783055c1625e7510d0c83b902875%2Ffind_adv1.png?alt=media)
6. Click the appropriate radio button for the status of the card type to be included in your search.

   <table><thead><tr><th width="126">Option</th><th>Purpose</th></tr></thead><tbody><tr><td>All</td><td>The default setting.<br>Performs a Cardholder find based on the configured parameters where the search is not limited by card enable/disable status.</td></tr><tr><td>Inactive</td><td><p>Performs a Cardholder find based on the configured parameters where the search will only return Cardholders with at least one inactive card. An inactive card is where:</p><ol><li>Card is disabled, OR</li><li>Current date/time is outside the bounds of scheduled activation and expiry date/times.</li></ol></td></tr><tr><td>Active</td><td><p>Performs a Cardholder find based on the configured parameters where the search will only return Cardholders with at least one active card. An active card is where:</p><ol><li>Card is enabled, AND</li><li>Current date/time is between the card's activation date/time and scheduled expiry date/time.</li></ol></td></tr></tbody></table>
7. Click the **Start Search** button.

   All cardholders issued with Contractor cards numbered between 10 and 50 display within the Search window.

</details>

<details>

<summary>Example 4-C</summary>

You may need to find out the owner of a car that needs to be shifted from where it is currently parked on site.

**Note:**

This example would only be possible if you had a [*Personal Data Field (PDF*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#pdf-personal-data-field)*)* set up for car registration.

1. Click the **General** tab.
2. Within the **Look in** field select "Cardholder".
3. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b4c2fdc366fc932c54c20ef9a9881e40665f0fdd%2Ffind_adv3.png?alt=media)
4. From the **Personal Data Field** drop-down list (currently populated with **-- All Personal Data Fields --** ), select "Car Registration".
5. In the field that is currently populated with **Any Value**, select "Contains" from the drop-down list.

   This enables the free-text field beside it.
6. Enter the registration number of the car that needs to be shifted in the free-text field.

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

   The cardholder who owns the car with the entered car registration number displays within the Search window.

</details>

<details>

<summary>Example 4-D</summary>

There is an option on the **Advanced** tab that allows a site to find out what card technologies Readers are using. This example demonstrates how to find out what HBUS Readers on your site are configured to accept MIFARE Classic or 125 kHz card technologies.

**Note:** Permitted Card Technology is configured on the **Advanced** tab of the readers properties.

1. Click the **General** tab.
2. Within the **Look in** field select "HBUS Reader".

   **Note:** The search will be limited to HBUS Readers. Likewise, if you selected "Cardax IV Reader", the search would be limited to Cardax IV Readers, and if you selected "Card Reader" the search would include both Cardax IV and HBUS Readers.
3. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aac3c61bf1cdcc73eb4b1a486af804e0db264103%2Ffind_adv4.png?alt=media)
4. Uncheck the first three options,leaving **MIFARE Classic** and **125 kHz** checked.
5. Click the **Start Search** button.

   The HBUS Readers that are configured to allow access via MIFARE Classic or 125 kHz cards display within the Search window.

</details>


---

# 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-4-advanced.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.
