> 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/product-advisories/historical-notices/command-centre-software-and-integrations/cardholder-properties-page-obsolescence-january-2022.md).

# Cardholder Properties Page obsolescence - January 2022

Cardholder property pages and all associated cardholder-specific administration functions – such as adding or deleting cardholders and viewing or updating cardholder information, including access, cards, personal details, images, history, notes, notifications, and competencies – will be removed from the Configuration Client from mid-2022 (version to be finalized). In addition, the following cardholder reports will also be removed:

* Access Report&#x20;
* Activity Report
* Summary Cardholder Report
* Detailed Cardholder Report
* Voltage Report
* Evacuation Report

This functionality has been replaced by Cardholder Viewers and Reporting capability within the Command Centre client and remains available from there. There are no part number or licensing changes as a result of this obsolescence. Customers will still be able to use other functions in the Configuration Client which require display or use of cardholder data, such as configuring Photo ID card layouts.


---

# 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/product-advisories/historical-notices/command-centre-software-and-integrations/cardholder-properties-page-obsolescence-january-2022.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.
