> 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/notifications/setting-cardholder-quot-email-quot-and-quot-mobile-quot-pdfs.md).

# Setting Cardholder "Email" and "Mobile" PDFs

### Introduction

Contact details are held in contact type Personal Data Fields, (i.e. "Address", "Phone", "Email" and "Mobile"). "Email" and "Mobile" type PDFs also have a notification check box editable at the cardholder level. They are set for individual cardholders, and assigned to cardholders via Access Groups, as is common with other PDFs.

**Note:** Notifications is a licensable feature.

### Procedure

1. Set up an "Email" and a "Mobile" contact type Personal Data Field for use with notifications.

   Refer to [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) for the procedure.
2. Optionally, on the **Type** tab of the Personal Data Field, check the **Default Notifications** checkbox.

   This provides a default value for this property when a PDF is first assigned to a Cardholder.
3. Assign the Personal Data Fields to an appropriate Access Group, as follows:
   1. Click **Manage** from the menu bar, then **Access Groups**.

      The **Access Group** List Window opens.
   2. Highlight the Access Group you want to assign Personal Data Fields to, and double-click the mouse button.
   3. Click the **Personal Data** tab.
   4. From the **Personal Data Field** List Window, select the Personal Data Fields created at Step 1.

      Drag and drop them into the **Personal Data** tab window.
4. On the **Personal Data** tab of the Cardholder, populate the "Email" and "Mobile" Personal Data Fields and ensure the **Notifications** checkbox is ticked.

   Refer to [Editing a Cardholders PDF data](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/editing-a-cardholders-pdf-data.md) for the procedure.

   **Notes:**

   * As long as the email addresses and mobile phone numbers entered are valid, checking the **Notifications** checkbox ensures that the Cardholders will receive email and/or SMS notifications.
   * Mobile phone numbers can include spaces or dashes. These will be removed for notifications using this number.
   * It is possible to setup more than one Email and/or more than one Mobile PDF, and have a cardholder receive notifications to more than one email account and/or mobile phone number.


---

# 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/notifications/setting-cardholder-quot-email-quot-and-quot-mobile-quot-pdfs.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.
