> 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.md).

# Cardholder Competencies

### Introduction

Cardholder Competencies address a gap in the way Cardholder’s access to zones can be specified. Using Access Groups a Cardholder need only belong to any group providing access to the zone. However there is a need (especially in the mining industry) to be able to block access to a Cardholder who lacks some certification or whose certification has expired (for example Health and Safety certificate, qualification to operate equipment, etc.).

**Notes:**

* It is envisaged that cardholders in the emergency services would be put in an Access Group that has "competency-exempt" status configured for all Access Zones. All other cardholders would be required to have the competencies, whatever Access Group they belonged to, or at least somewhat less general competency exceptions.
* A competency once created is never 'removed' from the system, regardless of whether it has been assigned to anything or not. It can always be found by using the "Include deleted items" option (on the **General** tab) of the Find Tool.
* The **Times** tab of the Find Tool includes a cardholder "Competency Expiry" option. Choosing this option returns all Cardholders who have competencies that are due to expire within the specified time-frame.
* Competency requirements are additional the normal access schedule restrictions.
* Each Cardholder Competency requires the following to be specified:
  * Competency Type
  * Expiry Date (defaults to blank to indicate that it does not expire)
  * Advance Notification Period in days (defaults to zero if no Expiry Date, otherwise defaults to seven days).
* Messages can be configured to display at [HBUS Terminals](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#hbus-terminal) and Remote Arming Terminals (when used in conjunction with a reader) or secondary displays via the Gallagher Controller API (FTCAPI), when cardholders present their cards, to inform them of upcoming expiry of competencies or competencies they are missing. However, messages will not display when the reader is assigned to an elevator car.
* In a multi-server system Competencies and Cardholder Competencies are replicated between servers according to the same rules as any other replicated items.
* The Cardholder Report, Access Report and Site Configuration Report all have the option to include competencies.
* Access granted or denied events from a reader that is assigned to an elevator car will not contain any competency details.

***

### Licensing

The use of competencies is controlled by a server license option which specifies the number of competencies allowed to be created in the system, as follows:

`[Limits]`\
`Competencies=X`

Where `X` is the number of competencies your site is allowed.

**Note:** Base license files include the use of one competency, (i.e. the license file entry will be `Competencies=1`). Sites with this type of license file will have access to the competency functionality, but will only be able to create one competency.

In a multi-server environment each server is independently licensed and the server of origin can create as many competencies as it is licensed for. Competencies can only be edited on the server they were created on, but are replicated across all other servers in the system. A competency can be assigned to any cardholder whether it was created on the local server or a remote server.

***

### Operator Privileges

<table><thead><tr><th width="228">Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>"View Site"</td><td>to display a competency.</td></tr><tr><td>"Configure Site" and "View Site"</td><td>create, update or delete a competency.</td></tr></tbody></table>

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Scenario: Accessing a zone restricted by cardholder competencies](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/scenario-accessing-a-zone-restricted-by-cardholder-competencies.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring Competencies](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/configuring-competencies.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Assigning Competencies to cardholders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/assigning-competencies-to-cardholders.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Adding Competencies to Access Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/adding-competencies-to-access-zones.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Overriding Operator Group Competencies](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/overriding-operator-group-competencies.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Reporting on Cardholder Competencies](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/reporting-on-cardholder-competencies.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Competency Bulk Changes](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/competency-bulk-changes.md)


---

# 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.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.
