> 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/site-installation/server-properties/competency-messages.md).

# Competency Messages

### Introduction

Cardholder Competencies, which is a licensable feature of Command Centre, allows sites to block access to certain zones for Cardholders who lack some certification, or whose certification has expired. This tab, which is only visible if your site is licensed for the Cardholder Competencies feature, allows you to modify the system-wide default messages for competencies.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Competency Messages** tab.

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

   This screen allows you to specify the default competency messages for each 'Message display device' that is required to show these messages.

   'Message displays devices' are:

   * HBUS Terminal, or
   * a secondary display device via the Gallagher Controller API.

   When a cardholder presents their card, one of the following messages may be displayed:

   * Competency Missing
   * Competency Expired
   * Competency Expiry due

   **Note:** When a competency is created, the competency's messages are set to the system-wide defaults configured here, however you can alter the messages for each competency.
3. Select the type of message string you wish to modify from the **Reader Message** drop-down list. The options are:
   * Competency Missing
   * Competency Expired
   * Competency Expiry due
4. Enter a string into the grid.

   This is achieved by typing in text and selecting the appropriate "Insertable Fields", from the **Event details** drop-down list where necessary, and clicking the **Insert** button.

   **Notes:**

   * There is no limitation on how many of each **Event detail** can be inserted, nor on how many different types of details can be put in the message.
   * The string 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.
     * Gallagher Remote Arming Terminals = 5 rows of approximately 20 characters per row (variable width fonts used)
   * The contents of the **Event details** drop-down list will vary based on what **Reader message** has been selected for modifying.

     The following **Event details** represent entities that can be named within Command Centre, and will all appear in the drop-down list for each message, except for numbers 3 and 4, which will only appear for the “Competency expiry due” message:

     1. Cardholder name \[CH]
     2. Competency name \[CO]
     3. Date of expiry \[DA]
     4. Days to expiry \[#D]
   * The message will display for the length of time configured in the **Duration** field (Default = 5 seconds), or until the next card is presented, whichever comes first. If the 'More' function key is pressed on the HBUS Terminal and there is less than 10 seconds until the display is due to expire, the time will be increased to 10 seconds.
5. 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.


---

# 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/site-installation/server-properties/competency-messages.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.
