> 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/viewer-configuration-overall-process/configuring-tiles/configuring-individual-tile-types/configuring-a-cardholder-details-tile.md).

# Configuring a Cardholder Details Tile

This tile displays details of a Cardholder. It can be configured to show details for:

1. the Cardholder selected from the Cardholder List (on a Cardholder Viewer), OR
2. the Cardholder who last badged or presented their finger at a Door (for *Challenge\**), OR
3. the Cardholder related to an Event.

{% hint style="info" %}
**\*Challenge**

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.
{% endhint %}

### How to configure

1. Double-click on **Cardholder Details** on the 'Tile Toolbox'.

   The Cardholder Details Tile appears on the Configuration Panel section of the screen in preview mode.

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

   **Note:** The preview of this tile will look different if you are adding it to a Monitor Site Viewer, (i.e. it will be blank until the door is configured). For other viewers, it will show the fields configured for display. This gives you an idea of what it will look like in Operational mode. The actual field labels are shown, including PDF names, however the data content is 'dummy data'.
2. Move the mouse over the Cardholder Details Tile you have added, and click on the **Click to configure** button that appears.

   The Cardholder Details Configuration pop-up displays.

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

   **Note:** If you are adding this tile to a Monitor Site Viewer there will be an additional **Source** section at the bottom for selecting a Door.
3. Enter an appropriate **Title** for this Tile.
4. Uncheck the **Show Tile Header** checkbox if you want the tile header to be removed in operational mode.

   **Note:** While this feature maximises the available screen real estate, be aware that Tile maximise/minimise can only be achieved using hot keys < **Ctrl** + **M** >.
5. Select the fields you want to display by clicking in the checkbox next to the name of the field.

   **Note:** Under 'Standard Fields', the **First Name**, **Last Name**, **Short Name**, **Description** and **Division** fields are all included automatically, (i.e. they are checked by default), but can be removed, as are the fields under 'Accessibility'.

   * **Disable cipher pad:** For added security, T20 Terminals and/or T21 Keypad Readers can be configured as cipher pads for Card + PIN (in Configuration Client), so that each time a user badges their card a randomised number keypad will display on the terminal/reader screen. This functionality is not suitable for visually impaired cardholders, therefore this field will allow you to disable this functionality for individual cardholders who are visually impaired.
   * **Extended Door Time:** This allows a door to remain unlocked for longer than normal for those cardholders who require it, (e.g. disabled people, couriers, delivery vehicles, etc.).
   * **PIN Exemption:** This allows cardholders to be exempt from PIN entry when entering an Access Zone that is configured to otherwise require 'Card+PIN' access credentials.
6. Do you want to include Personal Data Fields (PDFs)?

   <table><thead><tr><th width="85">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>click the <strong>No PDFs</strong> radio button.</td></tr><tr><td>all PDFs,</td><td>click the <strong>All PDFs</strong> radio button.</td></tr><tr><td>some PDFs,</td><td><ol><li>Click the <strong>Selected PDFs</strong> radio button.<br>A browse tool displays.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f592a51c740e075faec3784e6d257a67c673b6ac%2Fpdfs_to_include.png?alt=media" alt=""><br></li><li>If necessary, search for the Personal Data Field(s) you want to add to this tile by entering search criteria in the <strong>Search</strong> field.<br>The grid becomes populated with PDFs that match the search criteria.</li><li>Click the checkbox next to each PDF name you want to include, or click the <strong>Select All</strong> button if you want to include all PDFs.</li><li>Click the <strong>Add Selection</strong> button.<br>The pop-up closes and each of the Personal Data Field(s) that was selected individually appears beneath the button, with a check box to the left of it's name ticked. A PDF can be excluded from the Cardholder Details tile by unchecking the box.</li></ol></td></tr></tbody></table>

   \
   A field that is revealable (and the operator has privileges to view it) will display as "Hidden" with an eye icon on the right.\ <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-0477338e15d845067af159e2d393334c78089132%2Fpdfs_hiddenoncardholderdetailstile.png?alt=media" alt="" data-size="original">\
   After clicking "Hidden", it will be revealed either as a viewable or an editable field.
7. Select the **Salto Settings** that you want to apply to an individual cardholder.
8. Are you adding this tile to a Monitor Site Viewer?

   <table><thead><tr><th width="85">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 9.</td></tr><tr><td>yes</td><td><p>you must select a door for the <strong>Last Cardholder at Door</strong> field. The Cardholder who most recently badged a credential at this Door’s entry reader will have their details displayed in the tile.<br>To do this:</p><ol><li>Click the <strong>Select Door</strong> button.<br>A browse tool displays.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6fb121fe5bddc9238dd2b1ceb325ec21bfb474bb%2Fselectdoorpopup.png?alt=media" alt=""><br><br><strong>Note:</strong> Local and remote Doors are displayed.</li><li>Check the door you want to use.</li><li>Click the <strong>OK</strong> button.<br>The pop-up closes and the <strong>Select Door</strong> button changes to the name of the door you selected.</li></ol></td></tr></tbody></table>
9. Click the **Close** button.

   The preview mode of the Cardholder Details Tile now displays the title given, the actual field labels, including PDF names, however the data content is 'dummy data'.

   **Note:** The Cardholder Details Tile does not have a horizontal scroll bar on it, therefore if PDFs are included, it is important to size the tile according to the length of the PDF names. Checking the preview mode during configuration should highlight any issues.


---

# 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/viewer-configuration-overall-process/configuring-tiles/configuring-individual-tile-types/configuring-a-cardholder-details-tile.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.
