> 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/initiating-an-inactive-cardholder-bulk-purge.md).

# Initiating an Inactive Cardholder Bulk Purge

### Introduction

This procedure describes how to purge all cardholders stored in one of a specified list of divisions, where:

* the most recent activity on the cardholder exceeds a specified number of days, and
* the cardholder is not a visitor or host on an active visit, (i.e. a visit with a status of 'Scheduled' or 'In Progress'), for the purposes of Visitor Management (a licensable feature).

To perform this procedure operator's need both the "Bulk Change" and "Edit Cardholders" operator privileges. In addition, operator's need sufficient divisional and other privileges to carry out each individual change listed within a bulk purge.

**Note:** An Inactive Cardholder Bulk Purge can be scheduled to run at specific times, via a Macro. See [Macros](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros.md) for further details.

### 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. **Right click** and select **New\...Inactive Cardholder Bulk Purge**.

   The "Select Divisions" screen of the Inactive Cardholder Bulk Purges Wizard displays.

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

   All the divisions that need to be placed onto this screen can be dragged and dropped from either the **Division** List Window or the Find Tool can be used. In this procedure the **Division** List Window has been used.
3. Click **Configure** from the menu bar, then **Divisions**.

   The **Division** List Window opens.

   Select those divisions that have inactive cardholders that require purging, and drag and drop them into this screen of the Wizard.

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

   **Note:** When a division is dragged on, it's entire child hierarchy is dragged on also. In the above screen example, if the "Accounts" division is dragged onto the Wizard, the "Accounts Payable" and "Accounts Receivable" divisions will also be dragged on.
4. Specify the number of days it will be until a cardholder is classified as inactive, by entering a number in the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0226d3fd53060c567d3da7b61caf90f9f4321fb8%2Finactivech_noinactivedays.png?alt=media) field. (Default = 365 days; Limit = 1 -999 days)
5. Close the **Division** List Window.
6. Click the **Next** button.

   The "Remove Cardholders" screen of the Inactive Cardholder Bulk Purges Wizard displays.

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

   The **Cardholders To Be Purged** grid on the left is populated with the inactive cardholders from the chosen divisions.

   **Notes:**

   * An inactive cardholder is one where the cardholder last badged their card more than the specified number of days ago, and has not been modified in that time either. If they are associated with a visit somehow they will not be able to be deleted.
   * Cardholders that are part of an Operator Group will always be excluded even if they are not placed in the **Cardholders Excluded From Purge** grid (on the right).
7. Drag any cardholders you do not want to delete from the **Cardholders To Be Purged** grid (on the left) to the **Cardholders Excluded From Purge** grid (on the right).
8. Click the **Next** button.

   The "Save and Start the Bulk Change" screen of the Inactive Cardholder Bulk Purges Wizard displays.

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

   The **Summary of Changes** section provides a summary of the changes for you to check before proceeding.
9. Do you want to save this bulk change and it's settings before running?

   <table><thead><tr><th width="66">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 11.</td></tr><tr><td>yes</td><td>type in a name and description.<br><br><strong>Note:</strong><br>The <strong>Name</strong> field is limited to 60 characters and the <strong>Description</strong> field is limited to 200 characters.</td></tr></tbody></table>
10. Click the **Save** button.

    This Bulk Purge and its settings are saved and now displays in the **Bulk Changes** List Window.

    **Note:**

    The **Save As** button allows you to change an existing Bulk Purge and re-save it as a new Bulk Purge with a different name. If you open an existing saved Bulk Purge and click the **Save As** button without changing the name, a message displays indicating that a Bulk Purge with that name already exists.
11. Click the **Start** button.

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

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

    This screen shows the progress of the bulk purge. While in progress, the status of this bulk purge 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.

    **Notes:**

    * If you did not name and save the bulk change before clicking the **Start** button, while the "Applying Changes" screen displays, the bulk change will appear in the **Bulk Changes** List Window with a system-generated name, until is completes successfully, at which time the system will delete it. While it is active or if it fails, it will remain in the **Bulk Changes** List Window until an operator deletes it.
    * 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 purge, or to go back and edit it.

### Result

Selected cardholders have been deleted from the system.


---

# 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/initiating-an-inactive-cardholder-bulk-purge.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.
