> 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/licensable-features/card-layouts-designing-printing-encoding/overall-process/locating-the-cardholder.md).

# Locating the Cardholder

### Introduction

This procedure describes how to locate a Cardholder using the Find Tool. Although you could locate a Cardholder directly from the **Cardholder** List Window, the Find Tool allows you to search on something specific to a Cardholder, (e.g. Student ID), which can speed up the process.

### Procedure

1. Click **Monitor** from the menu bar, then **Find...**

   The **Find** tool opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d43b071570c3e82ee03ada4e0c0cf560cbb1c932%2Fpartfour.png?alt=media)
2. Click within the **Look in** field.

   From the displayed drop-down menu, click **Cardholder**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e26086fe39adf705656cea6d721998dc428079e9%2Flocate_cardholder.png?alt=media)

   For subsequent iterations, the **Find...** window remains open with the last selections that were made, and you will not need to perform Steps 1-2 again.
3. Click the **Advanced** tab.

   This tab allows you to define your search by using a personal data field, (e.g. "Student ID").
4. Select the **Personal Data Field** from the drop-down list, and if it is known, the **Card Type** from the drop-down list.

   **Note:**

   Once these options are selected you will not have to select them again when you search for the next cardholder.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ce8d9095cec188196bd7e06248dc4b37afcf6f66%2Fchold_advanced.png?alt=media)
5. If you are searching by Student ID, enter it in the blank field and click the **Start Search** button.

   The cardholder with that unique Student ID will display within the Search window.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9d30f577e5847757604fd44123f534bf71af9130%2Fsearch_result.png?alt=media)
6. **Right-click** on the Cardholder record to display the context menu.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-80c8e7c58aa48c3314c4dfb6967dc9967f9aaf11%2Fedit_chold_result.png?alt=media)
7. To check or update cardholder data, go to [Editing Cardholder Data](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process/editing-cardholder-data.md) next.

   If no cardholder or card data needs changing, return to Step 6 of the [Overall Process](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process.md).


---

# 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/licensable-features/card-layouts-designing-printing-encoding/overall-process/locating-the-cardholder.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.
