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

# Configuring a Cardholder Access Groups Tile

This tile displays the *Access Groups\** assigned to an individual 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" %}
**\*Access Groups**

A group of cardholders with identical access criteria. An Access Group also has privileges other than access, including the ability to escort visitors and to do manual overrides.
{% endhint %}

{% 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 Access Groups** on the 'Tile Toolbox'.

   The Cardholder Access Groups 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-a557398f72891557ade922509d3257fdf52f96f5%2Fcardholderag_previewmode.png?alt=media)

   **Note:** This example is how the tile preview will appear when being placed on a Cardholder Viewer. On other viewers the buttons for assigning, copying and removing Access Groups will not appear.
2. Move the mouse over the Cardholder Access Groups Tile you have added, and click on the **Click to configure** button that appears.

   The Cardholder Access Groups Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-24d6610d486a633b10a8dd1912b37b51666bbcab%2Fcardholderag_tileconfig.png?alt=media)
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. Click the **Close** button.

   The preview mode of the Cardholder Access Groups Tile now displays the title given.

   **Note:** The number of Access Groups a Cardholder can be assigned will vary, so it is important you size the tile accordingly.


---

# 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-access-groups-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.
