> 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-a-new-cardholder-bulk-change/competencies.md).

# Change Competencies

1. Select **Competencies**.

   The Change Competencies pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-eb0f79a3f563965119cad8f8ed4d3b7b2d1e18ca%2Fchangecompetencies_popup.png?alt=media)
2. Select the Competencies that need adding to and/or removing from the cardholders.
3. In the "Add these Competencies" section of this screen, the checkboxes under **Overwrite existing** indicate whether the values shown in the grid will override the appropriate field in the relevant cardholder competencies.
4. If you want to disable a competency, select it and click the **Disable** button.

   The Disable Competency pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cd21d212798271379fa499843ffe7491e0910d58%2Fdisablecompetency_popup.png?alt=media)
5. Do you want this competency to be re-enabled at any time?

   If **no**, go to Step 6.

   If **yes**, check the **Re-enable selected competencies automatically** checkbox and 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.
6. Click the **Disable** button.

   The Disable Competency pop-up closes and the **Disable** button is replaced with a **Re-enable** button.

   **Note:** When a disabled competency is selected, it can be re-enabled by clicking the **Re-enable** button.
7. Click the **OK** button.

   The Change Competencies pop-up closes.


---

# 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-a-new-cardholder-bulk-change/competencies.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.
