> 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/copying-all-cardholders-under-a-role.md).

# Copying all Cardholders under a Role

### Introduction

The **Copy all cardholders** feature allows you to easily select all cardholders that have a particular cardholder filling a role, and be able to drag-and-drop or copy-paste into the Cardholder Bulk Changes Wizard, to allow a simple change for all cardholders.

*For example:*

Graeme Jones is currently the Supervisor of 46 staff. However, Graeme is leaving and Barbara Smith is taking over his role of Supervisor. Rather than individually dragging and dropping all 46 cardholders into the Cardholder Bulk Changes Wizard so their Supervisor can be changed, the **Copy all cardholders** feature can be used.

### Procedure

1. Click **Manage** from the menu bar, then **Bulk Changes**.

   The **Bulk Changes** 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** and select **New\...Cardholder Bulk Change**.

   The "Select Cardholders or Access Groups" screen of the Cardholder Bulk Changes Wizard displays.
3. 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)).
4. Locate, and highlight, the cardholder in the role.
5. **Right click** and select **Properties**.
6. Click the **Relationships** tab.
7. Highlight the applicable Role, (e.g. Supervisor),within the **View Cardholder's Roles** grid.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4f80c996abed156d586bd502e581e675159487e6%2Frole_copyallcardholders.png?alt=media)
8. **Right click** and select **Copy all Cardholders under this Role**.
9. Move the cursor to the grid on the "Select Cardholders or Access Groups" screen of the Cardholder Bulk Changes Wizard.
10. **Right click** and select **Paste**.

    All the Cardholders in the list below the Role appear in the "Select Cardholders or Access Groups" screen of the Cardholder Bulk Changes Wizard.
11. Go to the [Initiating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-cardholder-bulk-change.md) procedure and perform Steps 5 - 31 to complete the bulk change.

### Result

A Cardholder Bulk Change has been initiated.


---

# 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/copying-all-cardholders-under-a-role.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.
