> 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/deployment-resources/support-tools-and-troubleshooting/move-cardholder-utility.md). # Move cardholder utility Move cardholders between access zones to simulate access movements for reporting. The Move Cardholder Utility moves all cardholders from one Access Zone to another. Use it to simulate access movements when cardholders cannot badge individually. {% hint style="info" %} This is a separate downloadable utility, not the in-product bulk-change feature. For mass cardholder edits inside Command Centre, see [Command Centre - Bulk Operations](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/operate/command-centre-bulk-operations.md). The utility is typically triggered from a hardware switch or a macro. See [Server - Using a Macro to run an application](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/configure/server-configuration/server-using-a-macro-to-run-an-applica.md), where it is the worked example, `MoveCardholders.exe`. {% endhint %} ### What it does When run, the utility moves all cardholders from one Access Zone to another Access Zone. ### Time on Site at a mine site This utility was deployed at a mine site that has a legal requirement to report "Time on Site" for all Gallagher cardholders. The most common way cardholders access the site is via bus. The customer's site has one primary gate which is access controlled, and buses enter and exit through this gate. Cardholders badge as they board the bus. A cardholder's "Time on Site" needs to start and end as they enter and exit through the gate. However, with many cardholders on a bus as it moves through the gate, it is not feasible to have each cardholder badge separately. This makes it impossible for Command Centre, natively, to report "Time on Site". The utility enables the following behavior: * When the bus travels through the gate, the bus driver flicks a switch to trigger the utility. This action moves all cardholders on the bus to an "Onsite" access zone to simulate a movement for each cardholder, generating an access event within Command Centre for each cardholder that can then be reported on. ### Command Centre versions supported A tick indicates a supported version: | v7.90 | v8.00 | v8.10 | v8.20 | v8.30 | v8.40 | v8.50 | v8.60 | v8.70 | v8.80 | v8.90 | v9.00 | | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | | ✓ | | | ✓ | ✓ | | ✓ | | | ✓ | | ✓ | Supported in v7.90, v8.20, v8.30, v8.50, v8.80, and v9.00. ### Release notes Release notes for each supported version (newest first): * [Release Note Move Cardholders Utility (v9.00)](https://media.gallagher.com/m/707ec1dce2b4d951/original/Release-Note-Move-Cardholders-Utility-v9-00.pdf) * [Release Note Move Cardholders Utility (v8.80)](https://media.gallagher.com/m/637ff6bf4f36e18b/original/Release-Note-Move-Cardholders-Utility-v8-80.pdf) * [Release Note Move Cardholders Utility (v8.50)](https://media.gallagher.com/m/6043dc7bc5e5eb88/original/Release-Note-Move-Cardholders-Utility-v8-50.pdf) {% file src="/files/NzyCgCNHPLx0vM284UlH" %} Release Note Move Cardholders Utility (v8.30) {% endfile %} {% file src="/files/8KaaH9xCFhJKs3xFrFjN" %} Release Note Move Cardholders Utility (v8.20) {% endfile %} {% file src="/files/mFLhI451m3rsSoGlj8ML" %} Release Note Move Cardholders Utility (v7.90) {% endfile %} --- # 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/deployment-resources/support-tools-and-troubleshooting/move-cardholder-utility.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.