> 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-up-roles.md).

# Setting up Roles

### Introduction

Notifications are required to be sent to Cardholders, supervisors, managers, or administrators/operators for cases of card expiry and competency expiry. Roles are therefore required to define the relationships between Cardholders - to route a notification to the appropriate person.

This procedure is split into two parts, as follows:

* Creating Roles, and
* Assigning Cardholders to the Roles

***

### Configuration

To set up roles, perform the following procedures in Gallagher Configuration Client:

<details>

<summary>Creating a Role</summary>

**Note:** Operators require either the "Edit Site" or "Edit Role Definitions" privilege to create, edit or delete a Role.

1. Click **Manage** from the menu bar, then **Roles**.

   The **Role** List Window opens (in grid view).
2. **Right click** and select **New\...Role**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).

   **Note:** Examples for the **Name** are Supervisor, HR Manager, Administrator, etc.
4. Click the **Notifications** tab.

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

   The options on this tab allow Cardholders in this Role to be notified of pending Card and/or Competency expiries for their staff, via email.
5. Both checkboxes checkboxes are enabled (checked) by default.

   Leave enabled the checkbox(es) required for this Role, deselect the checkboxes that are not required for this Role.
6. Click the **Notes** tab if you want to add a note(s) about this Role.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
7. Click the **OK** button to exit and save this Role.

</details>

<details>

<summary>Assigning Cardholders to Roles</summary>

Cardholders can either be assigned to Roles manually or by using the bulk change feature. This procedure describes the manual method. For the bulk change method, refer to [Assigning Cardholders to Roles via Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/assigning-cardholders-to-roles-via-bulk-change.md).

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** 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. Locate, and highlight, the cardholder to assign the Role to.
3. **Right click** and select **Properties**.
4. Click the **Relationships** tab.
5. From the **Role** List Window, select those Role(s) you want to assign to this Cardholder.

   Drag and drop them into the **Cardholder's Relationships** grid on the **Relationships** tab.

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

   **Note:** Multiple Roles can be assigned to a Cardholder, (e.g. each Cardholder can have one Supervisor, one Card Administrator, one Manager).
6. Click on the Role so it is highlighted.

   The **Role** field becomes enabled.
7. Drag and drop the Cardholder who fills this Role from the **Cardholder** List Window onto the Role in the **Cardholder's Relationships** grid.

   *For example:*

   Graeme Jones is Jane Smith's Supervisor, so Graeme Jones is dragged and dropped onto the Supervisor Role in the grid.

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

   **Notes:**

   * The **View Cardholder's Roles** grid on this screen displays a "read-only" view of any Roles that this Cardholder fills, and which Cardholders the Role is filled for. Click the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dbd0910108807d606a183525e745ef58ac247709%2Ftree2.png?alt=media) beside a Role to expand the list of Cardholders below it.

     *For example:*

     This Cardholder is a Team Leader for Jane Smith and Kelvin Roberts.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b2743fe491dfb4d1e6e351a27092caea9cdf96e4%2Fchold_roles.png?alt=media)
   * A Role's property pages and/or Cardholder's property pages can be opened from this window, by either:

     * double-clicking on the Role or Cardholder in the grid, or
     * right-clicking on the Role. A context menu displays, with the option to select either **Role Properties** or **Cardholder Properties**.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e32f74f78c66807b5781b83643e59da3c1cffbc6%2Frole_contextmenu.png?alt=media)
8. 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.

   **Note:** Ensure any Cardholder that fills a Role for other Cardholders has an email Personal Data Field (PDF) entered on the **Personal Data** tab of their properties. The email PDF must also be enabled for Notifications.

</details>


---

# 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-up-roles.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.
