> 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-management/notifications/setting-expiry-notification-threshold-values.md).

# Setting Expiry Notification Threshold Values

### Introduction

Supervisors/Managers need to be notified via SMS and/or Email when:

* a card is nearing expiry for one of their staff,
* a competency is nearing expiry for one of their staff.

**Note:** Individual Cardholders may also need to be notified of this via SMS and/or Email.

For this to occur, expiry threshold values need to be set for these access elements, so the system will generate events when the access is nearing expiry.

**Note:** Expiry notifications will not be sent for 'old' cards and competencies that have already expired.

### Procedure

1. Click **Configure** from the menu bar, then **Competencies**.

   The **Competency** 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 competency, and select **Properties**.
3. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-49ce871716cb8141382fd6fa30b6c809e0185e59%2Fcompetency_setuptab_v830.png?alt=media)
4. Set the **Advance notice period** to the value that is required to represent the number of days, weeks, months or years prior to competency expiry to initiate the warning notification.

   **Notes:**

   * The maximum equivalent period is 999 days.
   * This notice period also controls the period used to display competency expiry warning at a reader.
5. Ensure the **Enable competency expiry notification** checkbox is ticked.

   **Note:** The running of the daily expiry notifications does not send a notification for a competency that has expired by a date earlier than the current date, less the Advance notice period. If the Advance notice period is set to zero, competencies that have expired in the past 24 hours will still be notified at the time the daily expiry notifications are run.
6. Click the **OK** button.
7. Repeat Steps 2-6 for each competency requiring warning notification of expiry.
8. Close the **Competency** List Window.
9. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** 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)).
10. **Right click** on the required card type, and select **Properties**.
11. Click the **Setup** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a6e026d1c5b0229df0f6f57837f6a2dad2abfc6b%2Fcardsetup.png?alt=media)
12. Set the **Advance notice period** to the value that is required to represent the number of days, weeks, months or years prior to card expiry to initiate the warning notification.

    **Note:** The maximum equivalent period is 999 days.
13. Ensure the **Enable card expiry notification** checkbox is ticked.

    **Note:** The running of the daily expiry notifications does not send a notification for a card that has expired by a date earlier than the current date, less the Advance notice period. If the Advance notice period is set to zero, cards that have expired in the past 24 hours will still be notified at the time the daily expiry notifications are run.
14. Click the **OK** button.
15. Repeat Steps 10-14 for each card type requiring warning notification of expiry.

### Result

The values you have set default as the threshold values for each of the two expiry types held on the Cardholder properties, as follows:

<table data-header-hidden><thead><tr><th width="214.55560302734375"></th><th></th></tr></thead><tbody><tr><td><ul><li>Card expiry:</li></ul></td><td>The <strong>Until</strong> date and time on the <strong>Cards</strong> tab</td></tr><tr><td><ul><li>Competency expiry:</li></ul></td><td>The <strong>Expires</strong> date and time on the <strong>Competencies</strong> tab.</td></tr></tbody></table>


---

# 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-management/notifications/setting-expiry-notification-threshold-values.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.
