> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/cardholders-tab.md).

# Cardholders tab

This procedure describes the configuration on the **Cardholders** tab of the Global Settings for Mobile Devices.

1. Click the **Cardholders** tab.

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

   This tab allows you to configure the following:

   * any Personal Data Fields to be displayed on the Cardholder Details screen
   * fields to be used for manually searching for Cardholders
   * reasons for a Cardholder failing or passing a *challenge\**

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>*Challenge</strong></p><p>The Challenge feature allows a Command Centre operator to contest Cardholders as they attempt to gain access through a Door, and either grant or deny access.</p></div>

   **Note:** For instructions on how to configure Cardholder images refer to [Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/personal-data-fields/creating-a-new-personal-data-field.md).
2. The **Reasons for Failed Spot Check** grid allows you to pre-configure a list of reasons for a Cardholder either failing or passing the challenge.

   Add reasons as follows:

   1. Click the **Add Reason** button.

      An Add Challenge Reason pop-up displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cc32cb14c3878e789d23724d9be3af4dd2182ac5%2Faddchallengereason_popup.png?alt=media)
   2. Enter a **Reason** and click the **OK** button.

      The reason is added to the bottom of the list.

   **Notes:**

   * Reasons can be removed from the list by selecting the reason to be deleted and clicking the **Remove** button.
   * You can use the up and down arrows to the side to change the order of the reasons, (i.e. select the reason you want to move and click either the up or down arrow to move it).
3. The **Information to Display and Search by** grid shows the four types of information that can be displayed for a cardholder, (i.e. Personal Data Fields, Access Groups, Competencies and Cards).

   Configure what information you want displayed and whether it should be possible to search on that information type using the drop-down lists.

   **Notes:**

   * It is not possible to search for cardholders by Access Group or Competency.
   * You can use the up and down arrows to the side to change the order of the items, (i.e. select the item you want to move and click either the up or down arrow to move it).
   * The 'Display' and 'Search by' options you select for the Personal Data Field entry will determine whether or not the **Personal Data Fields** grid will be enabled or not.
4. The **Personal Data Fields** grid can display information needed to validate a Cardholder's identity and whether they should be where they are.

   **Note:** Your site may choose not to include any PDFs.

   Add the Personal Data Fields you want displayed and whether they can be searched on, as follows:

   1. Click the **Add Personal Data Fields** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6cfa1c2c8ff0c8d197a3dea925062fdb3549d440%2Fmobileclient_selectpdfs.png?alt=media)
   2. If necessary, search for the PDF(s) you want by entering characters in the **Search** field and/or refining the search mode and filters.
   3. Check the PDF(s) you want and click the **Add Selection** button.

      The browse tool closes, and the selected PDF(s) appear in the Personal Data Fields grid.
5. Return to Step 12 of [Configuring Global Settings for all Mobile Devices](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings.md) for configuration instructions for the other Global Settings tabs.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/cardholders-tab.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.
