> 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/products/cc-software/configure/workforce-management-solutions/cardholder-display.md).

# Cardholder display

Display cardholder details, access decisions, photos, cards, and competencies after badging.

Cardholder Display is a **standalone utility** that reads the Command Centre cardholder database and, next to a Gallagher card reader, displays cardholder information after badging: name, access decision, photo, Personal Data Fields, cards, and competencies. It runs in a **non-interactive** or **interactive** mode.

### What it can display

First and last name; access decision (Granted or Denied, plus the reason if denied); photo; Description; Personal Data Fields; Cards and expiry dates; and Competencies and expiry.

### Two modes

* **Non-interactive display:** the standby screen shows the lockdown status of a nominated Access Zone. After badging, the cardholder screen shows their details (and can also display Access Groups and expiry dates). It auto-logs off after a configurable timeout.
* **Interactive display:** the standby screen is a Welcome screen. After badging, the cardholder screen shows a series of **tabs** (touchscreen or mouse navigation), can access a 'Home' HTML page, and can display Competency expiry messages. The cardholder can log off manually or via auto-timeout.

**Versions supported:** v7.90, v8.00, v8.10, v8.30 or later.


---

# 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/products/cc-software/configure/workforce-management-solutions/cardholder-display.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.