> 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-notes-tile.md).

# Configuring a Cardholder Notes Tile

This tile can display notes recorded for 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 Notes** on the 'Tile Toolbox'.

   The Cardholder Notes Tile appears on the Configuration Panel section of the screen in preview mode. The data content displayed is 'dummy data' to give you an idea of what it will look like in Operational mode.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1b1cac6608fa280e72355f2f4f15f9bc4f8a2f37%2Fcardholdernotes_previewmode.png?alt=media)
2. Move the mouse over the Cardholder Notes Tile you have added, and click on the **Click to configure** button that appears.

   The Cardholder Notes Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-60b6058508e4e0f31228ebb460aa1282510c02f7%2Fcardholdernotes_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. Are you adding this Tile to a Monitor Site Viewer?

   <table><thead><tr><th width="66">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 6.</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 notes 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>
6. Click the **Close** button.

   The preview mode of the Cardholder Notes Tile now displays the title given, and still displays 'dummy data'.


---

# 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-notes-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.
