> 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/notifications-tab.md).

# Notifications tab

To enable email and/or SMS warning notifications for competency expiries, perform the following procedure:

1. Click the **Notifications** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cff4a3660b147880d6de294b1f17dbe6c05df22f%2Fcompetency_notificationstab1_830.jpg?alt=media)
2. Select the **Enable competency expiry notification** checkbox.
3. Configure as appropriate:

   <table><thead><tr><th width="174">Field</th><th>Description</th></tr></thead><tbody><tr><td>Notification warning period</td><td><p>Defines when Cardholders are sent warning notifications. It is the amount of time until a Cardholder's competency is set to expire when the Cardholder will be sent a notification.</p><p>For example, if a Notification warning period is set to 2 Weeks, a Cardholder will be warned (via email and/or SMS depending on Cardholder Personal Data) of their competency expiry two weeks before the Competency is set to expire.</p><p><strong>Note:</strong> Cardholders must have an Email PDF configured to receive email notifications, and a Mobile PDF configured to receive SMS notifications.</p></td></tr><tr><td>Roles to Cc for individual warning notifications</td><td>The Roles that will be carbon copied (Cc'd) in the email warning notifications that are sent to Cardholders. Remote Roles can also be added here.</td></tr><tr><td>Send summary to cardholder's role if within</td><td><p>Defines when a Cardholder's Roles are sent summaries of upcoming Cardholder competency expiries. It is the time period before a Cardholder's competency expires, within which, upcoming expiry summaries will be sent to Roles at the same times as all Notification warning period times. Summaries will be sent via email, not SMS. 'Roles' in this instance refers to all Roles in the <strong>Cardholder's Relationships</strong> grid in the <strong>Relationships</strong> tab of the Cardholder.</p><p>For example, if set to Always, a Cardholder's Roles will be sent summaries of their upcoming expiries at all Notification warning periods. If set to 2 Weeks, a Cardholder's Roles will be sent summaries of their upcoming expiries at Notification warning periods of two weeks or shorter.</p><p><strong>Notes:</strong></p><p>The time period options that appear in this list are purely reflective of the periods you set in the <strong>Notification warning period</strong> grid.</p><p>Roles are only sent summaries if <strong>Competency Expiry Warnings</strong> is selected in the Role's <strong>Notifications</strong> tab.</p></td></tr></tbody></table>

<details>

<summary>For a better understanding of these fields, click here to see a configuration scenario</summary>

<table><thead><tr><th width="130">Notification Warning period</th><th>Screenshot of configuration</th><th>Result</th></tr></thead><tbody><tr><td>3 Months</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-960bdaa311c0eb7a5bec70d2326bd0b793a05faa%2Fcompetency_scenario1_830.jpg?alt=media" alt=""></td><td>At 3 Months before expiry the Cardholder is notified. The Roles, 'Role 1' and 'Role 2', are Cc'd in the Notification. The Cardholder's Roles are not sent summaries because <strong>Send summary to cardholder's role if within</strong> is set to 10 Days, and the notification is being sent at 3 Months (which is not within 10 Days).</td></tr><tr><td>2 Weeks</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fa95cfa81dc4f71d3761b8fec98442f14ffe7d8a%2Fcompetency_scenario2_830.jpg?alt=media" alt=""></td><td>At 2 Weeks before expiry the Cardholder is notified. The Role, 'Role 1' is Cc'd in the Notification. The Cardholder's Roles are not sent summaries because <strong>Send summary to cardholder's role if within</strong> is set to 10 Days, and the notification is being sent at 2 Weeks (which is not within 10 Days).</td></tr><tr><td>10 Days</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-74e0d6b534eb2a67c9fba1c071c01c2c486d2ef9%2Fcompetency_scenario3_830.jpg?alt=media" alt=""></td><td>At 10 Days before expiry the Cardholder is notified. No Roles are Cc'd in the Notification. The Cardholder's Roles are sent summaries because <strong>Send summary to cardholder's role if within</strong> is set to 10 Days, and the notification is being sent at 10 Days.</td></tr><tr><td>2 Days</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ea3c58a4cae3fc59d3df1c6c9a662db5f310e117%2Fcompetency_scenario4_830.jpg?alt=media" alt=""></td><td>At 2 Days before expiry the Cardholder is notified. The Roles, 'Role 1' and 'Role 2', are Cc'd in the Notification. The Cardholder's Roles are sent summaries because <strong>Send summary to cardholder's role if within</strong> is set to 10 Days, and the notification is being sent at 2 Days (which is within 10 Days).</td></tr></tbody></table>

</details>

4. Right-click inside the **Notification warning period** grid and select **Insert...**

   A warning period is created.
5. Set the period of warning for this notification. From the drop-down list below the **Notification warning period** grid, select the unit of time. Then, using the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0bc30f01f1bd331098c189c9f7def73089354468%2Fcompetency_arrowbuttons_830.jpg?alt=media) buttons or manually, enter the amount of your selected unit of time (days, weeks, months) you want to set the warning period for.
6. Select the Roles to be carbon copied (Cc'd) in the notifications for this warning period. From the Roles window ( **Manage > Roles** ), drag and drop the Roles that you want to be Cc'd in individual warning notifications, into the **Roles to Cc for individual warning notification** grid.
7. For all additional Notification warning periods you wish to configure, repeat steps 4-6.
8. From the **Send summary to cardholder's role if within** drop-down list, select when you wish Roles to be sent summaries of upcoming Cardholder expiries.
9. The content of the email notifications can be customised. If you wish to customise the email notifications, refer to [Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications.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/configuring-competencies/notifications-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.
