> 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/quick-tips-for-working-with-bulk-changes.md).

# Quick Tips for working with Bulk Changes

* The Bulk Change function allows an appropriately privileged operator to perform a mass data edit on multiple items within a site's database. Two types of Bulk Changes can be configured:
  * **Cardholder Bulk Change** allows an operator to make one or more changes to several Cardholders in a single action.
  * **Inactive Cardholder Bulk Purge** allows for purging (deletion) of inactive Cardholder records.
* The icons associated with Bulk Changes in the Navigation Panel reflect their current run status. Hovering over an icon will display a pop-up indicating what the status is.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-85905c8207d2e3146b936db62d76961d8a64f924%2Fbulkchange_statusicons.png?alt=media)
* Selecting the **Allow Bulk Change to be run independently in the Cardholder Viewer** check box allows a Cardholder Bulk Change to be run directly from the Cardholder Viewer.
* Bulk Changes with unsaved changes display in the Navigation Panel in **bold** and have a **\*** at the end of their name.

### More information

For more information, refer to the topic *"Bulk Changes"* in the Gallagher Command Centre Online Help.


---

# 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/quick-tips-for-working-with-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.
