> 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/assigning-competencies-to-cardholders.md).

# Assigning Competencies to cardholders

### Introduction

This procedure describes how to assign competencies to cardholders.

**Note:**

The operator privilege required to update cardholder competencies may need to be different to "Edit Cardholder" as it may involve different staff, (e.g. HR) that provide this information. Operators with the "Edit Cardholder" privilege can alter the expiry times and enable/disable competencies, however they cannot add/remove competencies from a Cardholder. In order to do this they require the "View Site" privilege. This may be required when cardholder competencies are sourced from an external system via an external interface, (e.g. from an HR system).

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** 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** on the required cardholder, and select **Properties**.
3. Click the **Competencies** tab.

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

   The **Competency** List Window opens.
5. Select those competency(s) you want to assign to the cardholder.

   Drag and drop them into the **Competencies** tab.

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

   While the competencies are sorted in alphabetical order on the **Competency** List Window, when they are dragged into the upper grid on the **Competencies** tab, they are sorted according to expiry, with the competencies that are expired at the top (in red text), followed by those that will expire the soonest. If a competency is within the competency “warning period”, then it will be in yellow text. A competency that is disabled will be greyed out in the competency grid.

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

   **Note:** The specific shade of colour will change depending on the system colours, so with dark system text it would be a darker shade of red or yellow, and with light system text it would be a lighter shade.
6. Close the **Competency** List Window.
7. You can set the expiry date, add comments to, remove or disable a competency.

   <table><thead><tr><th width="234">If you want to...</th><th>then select the competency and...</th></tr></thead><tbody><tr><td>set an expiry date for a competency</td><td>use the <strong>Expires</strong> date and time control to set when the competency is due to expire.</td></tr><tr><td>disable a competency</td><td><p>click the <strong>Disable Competency...</strong> button.</p><p>The <strong>Re-enable Competency</strong> dialog displays, and the <strong>Disable Competency...</strong> button is replaced with the <strong>Re-enable Competency</strong> button.</p><p>If the competency is not to be re-enabled at any time, click the <strong>Manually</strong> radio button. However, if you want the competency to re-enable at a later date, use either the <strong>In</strong> control to specify the length of time until it will be re-enabled, or the <strong>On</strong> date and time control to set when it will be re-enabled.</p><p><strong>Note:</strong> When a disabled competency is selected, it can be re-enabled by clicking the <strong>Re-enable Competency</strong> button.</p></td></tr><tr><td>add a comment to a competency</td><td><p>enter your free-form text comments in the Comment grid. (Maximum = 2500 characters)</p><p><strong>Note:</strong> This information can be used as a historical record of changes.</p></td></tr><tr><td>remove a competency</td><td><strong>right click</strong> and select <strong>Remove from List</strong>.</td></tr></tbody></table>
8. If you want to run a Detailed Cardholder report based on the Cardholder being edited, click the **Run Cardholder Report** button.

   The Cardholder Report Wizard automatically advances to the **Report Generation Progress** page and the report starts running. Once the report has been generated, you can close and discard the report, or use the **Back** button in the report wizard to reconfigure or save the report.
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A competency(s) has been assigned to a cardholder.


---

# 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/assigning-competencies-to-cardholders.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.
