> 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/adding-competencies-to-access-zones.md).

# Adding Competencies to Access Zones

### Introduction

This procedure describes how to configure an Access Zone so that cardholders attempting to enter that zone are required to have competencies.

**Notes:**

* Adding Competencies to an Access Zone requires Command Centre to update the Competency details of all cardholders who have access to that zone. This can result in a delay before the Competency is in effect for all cardholders. The length of this delay will depend on the number of cardholders who have access to that zone, (e.g. 1000 cardholders may take several minutes to update). Therefore, the following process is recommended when changing larger numbers of cardholders to minimise the delay experienced:

  **Note:** This process is probably best performed at night when there is less activity on site and less chance of disruption.

1. Create the Competency.
2. Initiate a Bulk Change for the necessary Cardholders with the new Competency.

   **Result:** All relevant cards will be updated, although there are no changes since Competencies have not been linked to the Access Zone yet.
3. Add the Competency to the Access Zone, but leave it as "Not Enforced".

   **Result:** All relevant cards will be updated onto the Controller, and the Cardholders will still get access granted.
4. "Enforce" the Competency on the Access Zone.

   **Result:** Only the Access Zone's configuration is sent to the Controller.

* An Access Group can be made "competency-exempt" for a specified Access Zone, which means that cardholders belonging to that Access Group will not be subject to ANY competency checks in order to enter that Access Zone, (e.g. escorted visitors).

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** on the required Access Zone, 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-bb57fa0250effc9afc64da5e7a44824c2e05bc3f%2Faccesszone_competenciestab.png?alt=media)

   If this screen has not already had any competencies added to it, the **Required Competencies** section and the message text box below it are disabled. The **Required Competencies** section becomes enabled once a minimum of two competencies are added to the grid.
4. Click **Configure** from the menu bar, then **Competencies**.

   The **Competency** List Window opens.
5. Select those competency(s) you want to apply to this Access Zone.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4aed7758cdc3da4bb65237ab079a597bfa3e50eb%2Fcompetencies_into_accessz.png?alt=media)
6. Close the **Competency** List Window.

   **Note:** In the following example, the **Required Competencies** section has been enabled as a result of there being at least two competencies added to the grid.

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

   By default, the **All of the competencies are required** radio button is selected, and all competencies are enforced, which means that anyone wanting access to the zone will be denied access if they do not have these competencies.
7. Click the **Only one of the competencies is required** radio button if you require this option rather than all competencies being required.

   The message text box below it becomes enabled, allowing you to alter the message that will display at any 'Message display device' that is required to show these messages, (i.e. HBUS Terminal or a secondary display via the Gallagher Controller API).

   **Note:** The message that displays is limited depending on the type of reader, as follows:

   * Gallagher HBUS Terminals = 2000 characters (one byte characters or Latin characters). Four lines of text are displayed. A user can access the remaining text by pressing the 'More' function key on the HBUS Terminal, then scrolling the message.
   * Secondary devices via the Gallagher Controller API can display the complete message entered.
8. Check/uncheck the **Enforced** checkbox for individual competencies as required, or alternatively use the **Enforce all competencies** checkbox if you want ALL the competencies to be enforced/not enforced.

   **Note:** If you chose the **Only one of the competencies is required** option, then either ALL of the competencies need to be enforced, or none of the competencies are to be enforced. If you try to apply your changes with individual competencies enforced/not enforced, the following error message will display:

   *"If any competency is required to enter a zone then either all of the competencies must be enforced, or all of the competencies must be not enforced."*

   <table><thead><tr><th width="108">If...</th><th>then anyone wanting access to the zone will...</th></tr></thead><tbody><tr><td>checked</td><td>be denied access if they do not have that competency, unless they are exempt, (i.e. they belong to an Access Group listed as exempt on the <strong>Competency Exemptions</strong> tab).</td></tr><tr><td>unchecked</td><td>not be denied access. However appropriate warnings and events are generated.</td></tr></tbody></table>

   **Note:**

   The arrows to the side of the grid can be used to change the order of the competencies, (i.e. Select the competency you want to move and click either the up or down arrow to move the competency. This generates an event that indicates *"Changed: The order of competencies has changed"* on the **Details** tab of the Event properties window).

   The order determines which competency warning will be displayed if several of the competencies are missing or expired. However, no matter what order competencies are prioritised in, if there is more than one competency due to expire, an "expiry due" notification will display for the expiry that is due to expire first.

   Additionally, competency expired messages for **Enforced** competencies take precedence over "expiry due" notifications.
9. Click the **Competency Exemptions** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-521df7a8b87357fc2b72fa15c87187cb56083066%2Faccesszone_competencyexceptionstab.png?alt=media)
10. Click **Manage** from the menu bar, then **Access Groups**.

    The **Access Group** List Window opens.
11. Select those Access Group(s) you want to be exempt for this Access Zone, (i.e. the members of the Access Group will have the ability to enter the Access Zone even if they do not have the required competencies).

    Drag and drop them into the grid on the **Competency Exemptions** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8da9aae58d1705a30b0c031e134876755a502e4d%2Fag_into_accessz.png?alt=media)
12. Close the **Access Group** List Window.
13. 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 added to an Access Zone.


---

# 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/adding-competencies-to-access-zones.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.
