> 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-web-releases/2025/december.md).
# December
**Date Released:** 11/12/2025
### Quick View for Cardholders
**Available on:** Desktop
We’ve introduced Quick View, a streamlined way to confirm cardholder information without needing to open the full record.
#### Why we built it
Operators often need to scan through multiple cardholders to find the right one. Quick View helps you get the information you need - faster, reducing clicks and keeping you in your workflow.
#### Why it matters
Quick View provides essential context without breaking your workflow, making it easier to identify the correct cardholder and complete tasks faster in Command Centre Web.
#### How it works
Hover over a cardholder’s name and select » Quick View to instantly view key information in a right-hand panel.
#### What Quick View shows
**Identity & Status**
* Cardholder name
* Authorization status
* Last zone entered
**Personal Data**
* The top three Personal Data Fields (PDFs), determined by the site’s PDF sort order
* Only fields the operator is privileged to view will be displayed
**Recent Activity**
* The three most recent activities for the cardholder
**Credentials**
* Up to three assigned credentials, including status
**Access Groups**
* The first three access groups assigned to the cardholder
---
# 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-web-releases/2025/december.md?ask=&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.
