> 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/overriding-operator-group-competencies.md).

# Overriding Operator Group Competencies

### Introduction

This procedure describes how to override the default access of a competency for the operators in an Operator Group.

### Procedure

1. Click **Manage** from the menu bar, then **Operator Groups**.

   The **Operator Group** 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 Operator Group, 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-4568be86659be94342f6318c32556cb7177c8d87%2Fopgroup_competencyoverridestab.png?alt=media)

   By default, this tab will not be populated with any competencies. Instead, this Operator Group will get the privileges for competencies that are assigned at the competency level. If you want to override the default privilege to something else, you can drag competencies onto this tab.

   The level of operator privilege to view or edit cardholder information stored in a cardholder’s competency is determined for individual competencies. The competency privileges only apply to cardholders in the Operator Group’s Divisions (as configured on the **Divisions** tab).

   The default operator privilege for each competency is determined when the properties of the competency are configured. The default operator privilege can be overridden for each competency by selecting a new option.
4. Click **Configure** from the menu bar, then **Competencies**.

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

   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-88bbd1d1a59a6ff54fe4c0a90793e72ea942be87%2Fcompetencies_into_opgroup.png?alt=media)
6. Highlight the competency you wish to determine the level of operator privilege for.

   The contents of the **Field Access** groupbox become enabled.
7. Click the radio button for the privilege you require.

   <table><thead><tr><th width="102">Privilege</th><th>Description</th></tr></thead><tbody><tr><td>Hide</td><td>Operators will not see the cardholder information recorded for this competency, for cardholders in the group's Divisions.</td></tr><tr><td>View Only</td><td>Operators will be able to view cardholder information for this competency, for cardholders in this group's Divisions.</td></tr><tr><td>Edit</td><td>Operators will be able to enter, view, change and delete cardholder information for this competency, for cardholders in this group's Divisions.</td></tr></tbody></table>

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

   **Note:** To remove a competency privilege assigned to this Operator Group, **right click** on the competency and select **Remove from List**.
8. 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

The default access of a competency for the operators in an Operator Group have been overridden.


---

# 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/overriding-operator-group-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.
