> 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/configuring-competencies/competency-messages-tab.md).

# Competency Messages tab

To alter the messages displayed by this competency, perform the following procedure:

1. Click the **Competency Messages** tab.

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

   This screen allows you to specify how competency notifications are to be structured for each type of 'Message display device' that is required to show these messages. 'Message display devices' are:

   * [HBUS Terminal](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#hbus-terminal), or
   * a secondary display 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

   **Notes:**

   * When creating a new competency, the options on this tab are set to the system-wide defaults (via the Server Properties). Altering messages defined on this property page will only apply to this specific competency.
   * Competency messages are not displayed on a reader when the reader is associated with an elevator car.
2. Deselect the **Use Defaults** check box.

   The competency message becomes editable.
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 “Insertable Fields” from the **Event details** drop-down list, then clicking the **Insert** button, where necessary.

   **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 message string is limited to 2000 characters (one byte characters or Latin characters) or Gallagher HBUS Terminals. 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.
   * 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 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.
   * Only one cardholder competency message is displayed on the reader. The message that is displayed is decided as follows:
   * If there is one or more Competency Expiry Due message, the message for the competency that will expire soonest is displayed on the reader.
   * If there are messages for competencies that are due to expire at the same date and time, the Competency Expiry Due message for the competency ordered highest (on the **Competencies** tab of the Access Zone) is displayed on the reader.
   * If there are no Competency Expiry Due messages, only Competency Missing or Competency Expired messages, the message for the competency ordered highest (on the **Competencies** tab of the Access Zone) is displayed on the reader.


---

# 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/configuring-competencies/competency-messages-tab.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.
