> 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/licensable-features/cardholder-competencies/competency-bulk-changes.md).

# Competency Bulk Changes

### Introduction

This procedure describes how to initiate a bulk change of cardholder competencies in Command Centre. 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 change.

### Procedure

1. Perform Steps 1 - 4 of the [Initiating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-cardholder-bulk-change.md) procedure and then go to Step 2 of this procedure.
2. Click the **Next** button.

   The "Select Changes" screen of the Cardholder Bulk Changes Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-812d115568c98cde55bb6ee0cbd9d239c4d95a0c%2Fcholdbc_wizard3competencies.png?alt=media)
3. Click the **Modify Selected Cardholders** radio button, and tick the **Change Competencies** checkbox.
4. Click the **Next** button.
5. The "Change Competencies" screen of the Cardholder Bulk Changes Wizard displays.

   This screen allows you to select changes to make the cardholder competencies.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3dfb26e80c4f43842f1c6bf982559aa5ee100302%2Fcholdbc_wizard10.png?alt=media)
6. Click **Configure** from the menu bar, then **Competencies**.

   The **Competency** List Window opens.

   Select the Competencies that need adding to and/or removing from the cardholders, and drag and drop them into the appropriate grids on this screen of the Wizard, then close the **Competency** List Window.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1873e251970296c0b6ed8eba5d63adb5b69b7673%2Fcompintocholdbc.png?alt=media)
7. In the "Add Competencies" section of this screen, each checkbox next to **Overwrite** indicates whether the values shown in the grid will override the appropriate field in the relevant cardholder competencies. If the **Expiry**, **Disable state** or **Enable date** are changed, the relevant checkbox is automatically checked.

   **Note:** For cardholders that do not have the competency, what the competency values are set to for those cardholders will show in the "Add competencies" grid.
8. If you want to disable a competency, select it and click the **Disable Competency...** button.

   The **Re-enable Competency** dialog displays, and the **Disable Competency...** button is replaced with the **Re-enable Competency** button.

   If the competency is not to be re-enabled at any time, click the **Never** radio button. However, if you want the competency to re-enable at a later date, use either the **In** control to specify the length of time until it will be re-enabled, or the **On** date and time control to set when it will be re-enabled.

   **Note:** When a disabled competency is selected, it can be re-enabled by clicking the **Re-enable Competency** button.
9. Click the **Next** button.
10. Return to the [Initiating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-cardholder-bulk-change.md) procedure and perform Steps 28 - 31 to complete the bulk change.


---

# 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/licensable-features/cardholder-competencies/competency-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.
