> 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/configuration-client/site-management/bulk-changes/editing-and-running-a-saved-cardholder-bulk-change.md).

# Editing and Running a saved Cardholder Bulk Change

### Introduction

This procedure describes how to edit and 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.

### Procedure

1. Click **Manage** from the menu bar, then **Bulk Changes**.

   The **Bulk Changes** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight the bulk change that you want to edit and run, and **double click** the mouse button.
3. Has the bulk change been run before?

   <table><thead><tr><th width="240">If...</th><th>then the Bulk Changes Wizard opens at the...</th></tr></thead><tbody><tr><td rowspan="2">no, (i.e. it has no status in the <strong>Bulk Changes</strong> List Window)</td><td><p>"Select Cardholders or Access Groups" screen.</p><ol><li>Using the <strong>Next</strong> button, work your way through the Wizard, making any changes as necessary.</li><li>When you get to the "Save and Start the Bulk Change" screen, go to Step 4.</li></ol></td></tr><tr><td><strong>Note:</strong> If the Cardholder Bulk Change was configured in the Command Centre Client rather than the Configuration Client, AND it was configured with criteria, (i.e. advanced search rules), then the following message will display at the bottom of the wizard screen: <em>"The bulk change contains the following item selection criteria, which can be edited in the Command Centre client only"</em>.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9ace910202ecf9b666f405151d8f2b29cd06b189%2Fchbulkchange_createdinccclient.png?alt=media" alt=""></td></tr><tr><td>yes, (i.e. it has a status in the <strong>Bulk Changes</strong> List Window)</td><td><p>"Applying Changes" screen.<br>This allows you to view the results from the last time it was run.</p><ol><li>Using the <strong>Back</strong> button, work your way back through the Wizard to make any changes if necessary, or just go back to the "Save and Start the Bulk Change" screen to run it.</li><li>Go to Step 4.</li></ol></td></tr></tbody></table>
4. On the "Save and Start the Bulk Change" screen, the name and description of the existing bulk change populate the **Name** and **Description** fields.

   Do you want to save the changes to the existing bulk change or do you want to save these changes as a new bulk change?

   <table><thead><tr><th width="240">If you want to...</th><th>then...</th></tr></thead><tbody><tr><td>save the changes to the existing bulk change</td><td>click the <strong>Save</strong> button.<br>The bulk change will be re-saved with your edits made.</td></tr><tr><td>save this as a new bulk change</td><td>change the name and description, then click the <strong>Save As</strong> button.<br>Both the original bulk change and the newly named bulk change will display in the <strong>Bulk Changes</strong> List Window.<br><br><strong>Note:</strong><br>If you click the <strong>Save As</strong> button without changing the Name, an error message will display indicating that the Name must be changed.<br></td></tr></tbody></table>
5. Click the **Start** button.

   The "Applying Changes" screen of the Cardholder Bulk Changes Wizard displays.

   This screen shows the progress of the bulk change. While in progress, the status of this bulk change will show as 'Active' in the **Bulk Changes** List Window, 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.

   **Note:**

   If you click the **Stop** button while the bulk change is in progress, any changes already made when it is stopped cannot be cancelled, instead they are completed. If the **Stop** button is clicked, you get the option to end the bulk change, or to go back and edit it.

### Result

An existing (saved) bulk change has been edited and run.

### Hint

{% hint style="info" %}
**Deleting saved Cardholder Bulk Changes**

Refer to [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for the procedure on how to delete a saved Cardholder Bulk Change.

**Note:** A bulk change cannot be deleted if it is included in a macro.
{% endhint %}


---

# 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/configuration-client/site-management/bulk-changes/editing-and-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.
