> 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-management/cardholders/editing-a-cardholders-pdf-data.md).

# Editing a Cardholders PDF data

### Introduction

This procedure enables you to enter a cardholder's personal data into the [Personal Data Fields (PDFs](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#pdf-personal-data-field)).

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Locate, and highlight, the cardholder to edit.
3. **Right click** and select **Properties**.
4. Click the **Personal Data** tab.

   **Note:** If an Access Group containing PDFs has been assigned to this Cardholder, then the PDFs associated with the Access Group will display here. Otherwise, the grid will be empty.
5. **Right click** over the data section of the PDF that you want to enter cardholder data against.

   The Data Entry field for that PDF is enabled.

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

   **Note:** Personal Data Fields with either "Revealable" or "Revealable and Editable" accessibility display **-- Click To Reveal --** in the Data Entry field. This accessibility is set on the **Type** tab of the Personal Data Field properties.

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

   With the appropriate privileges, operators can either view or create and edit the value of a Personal Data Field by clicking on **-- Click To Reveal --**, and then clicking the **Reveal** button that displays.

   The Default Notifications checkbox will be revealed when the **Reveal** button is pressed, (i.e. it is a blank space until that happens).

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

   For further detail regarding "Revealable" and "Revealable and Editable" accessibility, and the operator privileges required, see [Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md).
6. Enter the appropriate personal data.

   **Notes:**

   * Images, (e.g. corporate logos, cardholder photographs, etc.), can be captured and used for "Image" PDFs. Refer to [Capturing an Image](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/capturing-an-image.md) for the procedure.
   * By clicking on a "Date" PDF, a Date control appears. No date value is assigned if the checkbox is unchecked.

     A date must be supplied for required PDFs.
   * By clicking on a "Text - List" PDF, a pre-defined drop-down list appears.

     If it is a **Restricted** "Text - List" PDF, a cardholder can only have values populated from the pre-defined list, or a blank value. However, if it is **Unrestricted**, free text entry is allowed.
   * The **Notification** column contains a checkbox only for "Mobile" and "Email" type PDFs. When these checkboxes are ticked, it indicates that the PDF value is used in the Notifications feature for sending and receiving notifications, (i.e. "Mobile" for SMS and "Email" for Email notifications).
   * By clicking on a "Text" type PDF, or any of the contact type PDFs, (i.e. "Address", "Phone", "Email" or "Mobile"), a text box appears at the bottom to describe the regular expression syntax if the **Use Regular Expression** feature was enabled and defined on the PDF's **Type** tab.

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

     **Note:** On applying the changes, an error message box will display of the PDF data entered does not meet the regular expression syntax.
7. Repeat Steps 5-6 for each PDF.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6c3bcde59968eef25d7fb53cf64a3235fd3627d1%2Fpdfdata.png?alt=media)
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

The cardholder now has personal data recorded against the PDFs.


---

# 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-management/cardholders/editing-a-cardholders-pdf-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.
