> 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/personal-data-fields/understanding-personal-data-fields.md).

# Understanding Personal Data Fields

Personal Data is information that is stored for an individual cardholder. This information can include items such as car license plate, date of birth, signature, photographs, company division, etc.

Personal Data Fields (PDFs) are created as separate entities and are attached to [*Access Groups*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-group). Cardholders inherit the Personal Data Fields from the Access Group(s) they belong to.

When viewing a cardholder's record, it will contain all the Personal Data Fields specified in the Access Group(s) the Cardholder belongs to.

There are nine different types of Personal Data Fields, as follows:

* Text (an operator may enter any free hand text)
* Text - List (if "Restrict to List" is enabled, an operator may select from a list of pre-defined entries or leave it blank. If "Restrict to List" is not enabled, free text entry is allowed)
* Numeric
* Date
* Image (an operator may capture an image, e.g. signatures, cardholder photographs, etc.)
* Address
* Phone
* Mobile
* Email


---

# 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/personal-data-fields/understanding-personal-data-fields.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.
