> 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/cardholders/re-issuing-a-card-for-a-cardholder.md).

# Re-issuing a Card for a Cardholder

### Introduction

If a card is replaced, you do not need to go through the process of creating a new card; you can simply increment the issue number from the Cardholder properties.

A card may need to be replaced if the cardholder has lost their card, for example.

### Procedure

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 edit.
3. **Right click** and select **Properties**.
4. Click the **Cards** tab.
5. Click on the card you want to re-issue.
6. Click the **Issue Level** button.

   The Reissue Card pop-up displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c039e87bcf60c5e7054e158c79ae4c0ef7d93606%2Freissuecardpopup.png?alt=media)
7. The Issue Level of the card needs to increment by one.

   Ensure the number that defaults into the **Next issue level** field is correct.
8. Select the appropriate reason for why you are re-issuing the card, (e.g. Lost, Damaged, etc.) from the **Change reason (Card Status)** drop-down of available card states.
9. Click the **OK** button.

   The Reissue Card pop-up closes and the number of the **Issue Level** button has incremented by one.
10. 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.

### Result

The card has been re-issued.


---

# 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/cardholders/re-issuing-a-card-for-a-cardholder.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.
