> 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/understanding-bulk-changes.md).

# Understanding Bulk Changes

The bulk changes feature provides an automated method of changing a common set of properties on a group of items in Command Centre. Bulk changes can be scheduled to run at specific times. This is achieved using the Macro functionality. See [Macros](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros.md) for further details.

Only one bulk change can be run at one time. If an operator attempts to start a bulk change when there is already one running the second one will be queued and run once the first one has finished. Likewise, if bulk changes are scheduled to run (via macros), they will be queued and run in the order scheduled, with only one being executed at a time.

**IMPORTANT:**

As authorisations will not be checked before a bulk change is run, an operator with the "Bulk Change" operator privilege will be able to see any data that is contained in a bulk change that has been saved. Even if they do not have the privilege to view the data any other way, they will be able to see it in the bulk change.

*For example:*

A bulk change may contain a number of cardholders or Access Groups that the bulk change editor does not have access to view. However, in the bulk change they will be able to see this information.

### Bulk Changes List Window

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).

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-03b5c7789df475b863d5d6570b6d59ffda28eeb2%2Fbulkchangesmlw.png?alt=media)

All saved bulk changes are listed in this window. For each bulk change the operator who last edited it, the date and time it was last edited, and the status of the bulk change is provided. If a bulk change has only been saved but not executed, the status will be blank. A bulk change that has been successfully completed shall remain on the 'Successful' status until the next time it is edited, at which time it will revert to blank.

<table><thead><tr><th width="204">Status</th><th>The bulk change...</th></tr></thead><tbody><tr><td>Blank</td><td>has no status. The bulk change either has not been run or it has been redefined/saved since the last run.</td></tr><tr><td>Active</td><td>is running.<br><br><strong>Note:</strong> Bulk changes go through a run twice to check if any items that were locked during the first run are now unlocked.</td></tr><tr><td>Cancelled</td><td>is idle, having been stopped due to an operator cancelling the operation.</td></tr><tr><td>Queued</td><td>is queued waiting for another bulk change that is running, to complete.</td></tr><tr><td>Successful</td><td>is idle, having completed with 100% success.</td></tr><tr><td>Failed</td><td>is idle, having completed with less than 100% success.</td></tr><tr><td>Failed -- Server Interruption</td><td>has failed due to a server failure while the bulk change is active or queued.</td></tr></tbody></table>

**Note:** Saved bulk changes can be added to the Status Viewer.


---

# 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/understanding-bulk-changes.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.
