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

# Creating an Inactive Cardholder Bulk Purge

Perform the following procedure to create an Inactive Cardholder Bulk Purge:

**Notes:**

* To perform this procedure operators need both the "Bulk Change" and "Delete Cardholders" operator privileges. In addition, operator's need sufficient divisional and other privileges to carry out each individual change listed within a bulk purge.
* 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/command-centre-client/configuring-command-centre/administration/macros.md) for further detail.

1. Click the **New Bulk Change** button on the Viewer Navigation Panel, and then **Inactive Cardholder Bulk Purge**.

   The new Inactive Cardholder Bulk Purge is added to the Viewer Navigation Panel, and the Bulk Change Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e8812e9d290b96acab89ad9493f0893f17499065%2Fbulkpurgeinactiveconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Bulk Purge, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this not the appropriate Division for this Bulk Purge to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Bulk Purge at a later stage.
5. Click the **Close** button.

   The Bulk Change Configuration pop-up closes.

   There are two tabs, (i.e. **Change** and **History/Notes** ). The **Change** tab displays by default.
6. Click the **Select Cardholders by Divisions** button to select all the cardholders that require changing.

   The Cardholder Selection pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-406d54a6a503d7acf4cd89d0b3aeb528f20bec4a%2Fcardholderselection_popup.png?alt=media)
7. Click the **Select Divisions** button.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
8. Check the Division(s) that have inactive cardholders that require purging.

   The **Deselect All** and **Add Selection** buttons are enabled.

   **Note:** When a division is selected, its entire child hierarchy will be selected also.
9. Click the **Add Selection** button.

   The browse tool closes, and the selected Division(s) appear in the grid below the **Select Divisions** button.

   **Note:** The **Deselect All** and **Select All** buttons allow you to alter which Divisions you include.
10. Specify the period of inactivity that will classify a cardholder as inactive. There are two options, as follows:
    * **Modified** - The cardholder record has not had any changes, i.e. no modification was made to the cardholder, (e.g. change name, description, or add/remove cardholder to/from access groups,etc.) within the specified number of days.
    * **Access** - the cardholder has not used any access credentials and has not been in any Access Zone with for the period specified, i.e. no access information can be found, or the last access is before the specified number of days.
11. Click the **OK** button.

    The Cardholder Selection pop-up closes and the ‘Cardholders to be purged’ grid is populated with the cardholders that meet the inactivity criteria.

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

    **Note:** Cardholders that are part of an Operator Group will always be excluded even if they are not placed in the in the 'Excluded' column.
12. If there are any cardholders in the ‘Cardholders to be purged’ grid that you want to exclude from the bulk purge, tick the checkbox beside the cardholder (in the 'Excluded' column).

    The cardholder is now displayed in red italics.
13. Additional cardholders that do not meet the inactivity criteria, and therefore do not appear in the grid, can be added as follows:
    1. Click the **Add Cardholders to Exclude** button.

       The Select Cardholders pop-up displays.

       ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4282590ed2df6fcd449a33720cac15b180cd9620%2Fselectcardholders_popup.png?alt=media)
    2. To find the cardholder, select what criteria you want to search on from the **By** drop-down list, (i.e. Name, Description, Division, Card Number, Last Zone Entered, Authorised or All).

       By default, Name is selected.
    3. Start entering characters in the **Search** field.

       A minimum of 3 characters starts the search. However, if you selected Card Number(s) as the search criteria, you need to click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f1056e058547589bcd63a07bc872a1a741ea174c%2Fsearchbutton.png?alt=media) button after you enter a number in the **Search** field.
    4. From the search results, click on the cardholder(s) you want.

       The cardholder(s) appear in the lower section and are all checked by default.
    5. Uncheck any cardholders you do not want, and click the **OK** button.

       The pop-up closes and the cardholder(s) appear in the ‘Cardholders to be purged’ grid in blue italics.
14. If you want to record any note(s) about the Cardholder Bulk Change, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
15. Click the **Save** button.

    The Bulk Purge and its settings are saved has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Inactive Cardholder Bulk Purges**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Inactive Cardholder Bulk Purges.
{% endhint %}

{% hint style="info" %}
**Duplicating Inactive Cardholder Bulk Purges**

Operators privileged to create Inactive Cardholder Bulk Purges can also duplicate them, which makes the task of setting up multiple Inactive Cardholder Bulk Purges that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% 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/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-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.
