> 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/using-command-centre/working-with-viewers/cardholder-viewer/searching-for-cardholders-in-a-multi-server-environment.md).

# Searching for Cardholders in a multi-server environment

Cardholders are global items, so no distinction is made between those that were created locally or remotely when returning Cardholders in the search results.

When Cardholder search results are returned:

1. If the Cardholder was last identified at a site supported by the local server, the zone recorded in the Last Zone Entered column will be correct (unless there have been connectivity issues between the hardware and the server).
2. If the Cardholder was last identified at a site supported by a remote server, and the local server has cardholder location aggregation enabled for that remote server, the zone recorded in the Last Zone Entered column will be correct (unless there have been connectivity issues between the hardware and the server).
3. If the Cardholder was identified at a site supported by a remote server, and the local server does not have cardholder location aggregation enabled for that server, the zone recorded in the Last Zone Entered column will show the name of the 'Root' Division on the remote server the Cardholder was last identified at.

**Notes:**

* The Cardholder search results show the values applicable at the time the search was run. Hence the Last Zone Entered value may have changed.
* If the Cardholder is at a site supported by a remote server that is **not** aggregated with the local server, the date and time that appears in the Zone Entered Time column will be the date and time the local server was notified the Cardholder was at the remote server.


---

# 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/using-command-centre/working-with-viewers/cardholder-viewer/searching-for-cardholders-in-a-multi-server-environment.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.
