> 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/configuring-command-centre/administration/bulk-changes/editing-and-or-running-a-saved-cardholder-bulk-change.md).

# Editing and/or Running a saved Cardholder Bulk Change

This procedure describes how to edit and/or run an existing bulk change in Command Centre. To perform this procedure operator's need both the "Bulk Change" operator privilege as well as the appropriate item editing privilege.

**Notes:**

* When a bulk change is run, it uses ALL privileges an operator has, regardless of their currently selected system view. For example, an operator may exclude an operator privilege from their current system view, but if a bulk change is run, that privilege will form part of the operator privileges under which the bulk change will run.
* Bulk changes are subject to any workstation restrictions in place on the workstation at which it is run.

1. Click on the Bulk Change from the list in the Viewer Navigation Panel.
2. Do you want to edit the Bulk Change before running it?

   <table><thead><tr><th width="84">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 3.</td></tr><tr><td>yes,</td><td><ol><li>Make any necessary changes.<br>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change.md">Creating a new Cardholder Bulk Change</a> or <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-an-inactive-cardholder-bulk-purge.md">Creating an Inactive Cardholder Bulk Purge</a> for further detail if required.</li><li>Click the <strong>Save</strong> button.</li></ol></td></tr></tbody></table>
3. 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.
4. 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 with other bulk changes.</td></tr><tr><td>the bulk change is still selected in the Navigation Panel,</td><td>the <strong>Run Bulk Change</strong> button changes to the <strong>Display Progress</strong> button.</td></tr></tbody></table>
5. Click the **Close** button.

   An existing (saved) bulk change has been run.

   **Note:** Once a bulk change run has completed, the results can be found in the **History/Notes** tab. If any items failed to change, viewing the details will give you an idea of what caused the failure.

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


---

# 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/configuring-command-centre/administration/bulk-changes/editing-and-or-running-a-saved-cardholder-bulk-change.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.
