> 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/editing-cardholder-data.md).

# Editing Cardholder Data

### Introduction

It may be a good idea to check that a cardholders data is correct prior to printing and/or encoding a card for them. This procedure allows you to check the data and change if necessary.

### Before you begin

Before you begin this procedure ensure you have located the Cardholder using either the Find Tool or directly from the **Cardholder** List Window. From either window, you should have already right-clicked on the Cardholder record resulting in the context menu displaying.

### Procedure

1. From the context menu, click on **Properties**.

   The **General** tab of the Cardholder properties displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b42cfb33b12a77fbfe05e8719a024a74cfb5b6d3%2Fchold_general.png?alt=media)
2. If you wish to update personal data, (e.g. capture a cardholder image), click on the **Personal Data** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0b47debf4b23d70a700e0a9b42b87f043cf8e38f%2Fchold_personaldata.png?alt=media)
3. Double-click on the "Cardholder Image" personal data field to capture a new image. You can either capture an image from a camera installed on the workstation or upload an image from file. The former method lets you upload an image from a digital camera that installs as a removable drive on the workstation. If you use the latter method, a dialog box displays for you to path your way to the required folder. The path is remembered so that you do not need to repeat this step for the next cardholder.

   You can crop the image if necessary and then click **OK** to save it to the personal data field.
4. Other personal data fields can be edited by clicking on them.
5. If you need to add or check card data, click on the **Cards** tab.

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

   From this window you can view existing card details and add or delete cards if required.

   **Note:**

   Refer to [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for a full explanation of the fields on this tab.
6. Click **OK** to return to either the **Cardholder** List Window or the **Find...** window.
7. Return to Step 7 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/editing-cardholder-data.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.
