> 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/running-bulk-changes-from-the-cardholder-viewer.md).

# Running Bulk Changes from the Cardholder Viewer

Providing an operator has the correct privileges, a bulk change can be viewed, edited and/or run from the Cardholder Viewer, as follows:

1. Click the **Cardholder Viewer** button on the Command Centre toolbar.

   The Cardholder Viewer opens.
2. Select one or more cardholder records in the Navigation Panel.
3. Click the **Actions** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fdaa06d9f9f80d95be6245a8a5e1fe3b27fb7eb8%2Fchold_actionsdropdown.png?alt=media)
4. Select **Bulk Change** from the drop-down.

   A Bulk Changes pop-up appears listing all the available bulk changes.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-17d07a7f093bbf9ece32174fc68987fc17ffff3a%2Fbulkchanges_popup.png?alt=media)
5. Select the bulk change that you want to run, and click the **Run Bulk Change** button.

   The message *“Some Bulk Changes may impact system performance. Are you sure you want to run this now?”* displays.
6. Click the **Yes** button.

   The Run Bulk Change pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d1e20ff25f30b1c39760d550de5b4418ddbd27bd%2Frunbulkchange_popup.png?alt=media)

   This screen shows the progress of the bulk change. While in progress, the status of the bulk change will show as ‘Active’ in the Viewer Navigation Panel, and if it completes successfully, (i.e. the progress bar reaches 100%), the status will change to ‘Successful’. When it completes the number of cardholders changed displays.

   **Notes:**

   <table><thead><tr><th width="282">While the bulk change is in progress, if..</th><th>then...</th></tr></thead><tbody><tr><td>you click the <strong>Stop</strong> button,</td><td>any changes already made when it is stopped cannot be cancelled, instead they are completed. If the <strong>Stop</strong> button is clicked, you get the option to end the bulk change, or to go back and edit it.</td></tr><tr><td>you click the <strong>Close</strong> button,</td><td>the Run Bulk Change pop-up will close and the bulk change will continue to run in the background while you continue working in the Cardholder Viewer.</td></tr></tbody></table>
7. Click the **Close** button.

   An existing (saved) bulk change has been run.


---

# 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/running-bulk-changes-from-the-cardholder-viewer.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.
