> 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-a-new-reader-bulk-change.md).

# Initiating a new Reader Bulk Change

### Introduction

This procedure describes how to initiate a new reader bulk change in Command Centre. A reader bulk change can be performed to change the card technologies accepted at readers.

### 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\...Reader Bulk Change**.

   The "Select Readers" screen of the Reader Bulk Change Wizard displays.

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

   All the readers that require changing need to be placed onto this screen, by dragging and dropping them from the appropriate List Window, or the Find Tool can be used.

   **Note:** You can use the Find Tool to locate all the readers you want to change the card technologies for, and then drag the search results onto this screen. See [Example 4: Advanced](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool/examples/example-4-advanced.md) (Example 4-D) for further detail.
3. Click the **Next** button.

   The "Select Permitted Card Technology" screen of the Reader Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-eb55b86e61270fbf8ee3b74257617e905f33cf43%2Freaderbulkchange_selectcardtechnology.png?alt=media)
4. In the Permitted Card Technology section, **Use the server settings** is selected by default.

   If you want to select other types of cards to be accepted at the reader, uncheck the **Use the server settings** checkbox and select the appropriate checkboxes.
5. If your site is using MIFARE Plus cards with the ‘X’ feature set and you wish to prevent relay attacks occurring over HBUS, check the **MIFARE Plus** checkbox to enable the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.
6. Check the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.

   The terminal will perform proximity checks when reading a MIFARE Plus X card.

   **Notes:**

   * Checking this option disables all other card technologies.
   * The MIFARE Plus X Card Proximity Checking feature will only work if the site that issued the card is using the same MIFARE Plus/DESFire key seed as your site.
   * Operators need the "Edit Site" privilege to be able to amend this setting.
7. Click the **Next** button.

   The "Save and Start the Bulk Change" screen of the Reader Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f5060d5da62f5154a874dbcdf4a6d048647347d0%2Freaderbulkchange_save.png?alt=media)
8. Do you want to save this bulk change and it's settings before running?

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

   This Bulk Change 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 Change and re-save it as a new Bulk Change with a different name. If you open an existing saved Bulk Change and click the **Save As** button without changing the name, a message displays indicating that a Bulk Change with that name already exists.
10. Click the **Start** button.

    The "Applying Changes" screen of the Reader Bulk Change Wizard displays.

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

    This screen shows the progress of the bulk change.

    While this screen displays, the bulk change will appear in the **Bulk Changes** List Window with a system-generated name. While in progress, the status of this bulk change will show as 'Active' in the **Bulk Changes** List Window, and if it completes successfully it will show as 'Successful', at which time the system will delete it.

    **Note:** While a Bulk Change of Readers is active, or if it fails, it will remain in the **Bulk Changes** List Window until an operator deletes it.

### Result

A Bulk Change of Readers has been initiated, and the selected readers have had the card technologies that are accepted at them changed.


---

# 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-a-new-reader-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.
