> 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/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/card-or-credential-details-to-change-card.md).

# Change Card or Credential Details (to change Card)

1. Select **Card or Credential Details**.

   The Change Card or Credential Details pop-up displays.
2. Select the **Card Type** you require from the drop-down list, or click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-eb8b7e19f56793693de4c172c25d4dd7bf3e4fbf%2Fselectcardtype_button.png?alt=media) button to use the Card Type browse tool to make your selection.
3. Do you want to remove or modify the selected card type for cardholders?

   <table><thead><tr><th width="120">If...</th><th>then...</th></tr></thead><tbody><tr><td>remove,</td><td>click the <strong>Remove Card</strong> radio button, optionally enable <strong>Only credentials with state</strong> and choose the credential state to remove, then go to Step 5.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8c733536acfd5c0645ce5b1511f9d3a9a1763bb3%2Fchangecardorcredentialdetails_popup.png?alt=media" alt=""></td></tr><tr><td>modify,</td><td>click the <strong>Modify Card</strong> button and go to Step 4.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fe30e3d6439e23598fc494f547c5fe69a4db9754%2Fchangecardorcredentialdetails_popup2.png?alt=media" alt=""></td></tr></tbody></table>
4. Configure the changes you want to make as necessary.

   One or more of these options can be selected.

<details>

<summary>Click here for a description of the options on this screen</summary>

<table><thead><tr><th width="184">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Increment Issue Level</td><td>Check if the selected cardholders require bulk incrementation of card issue level.</td></tr><tr><td>Enable/Disable Card</td><td>Choose to either enable or disable the card by checking the appropriate checkbox.</td></tr><tr><td>Change Card Type</td><td><p>Check if the card type of the card for the selected cardholders requires changing. When ticked, the drop-down field is enabled allowing you to select a different card type.<br><br><strong>Notes:</strong></p><ul><li>Only card types with the same Card Number Formats can be exchanged.</li><li>Only those card types that you have view privileges for will appear in the drop-down list.</li><li>If a cardholder has more than one card of a Card Type, they will all be changed unless one card fails to update. When a card fails to update, no cards for that particular cardholder will be updated.</li><li>Only cards in a non-customised card state at the time the bulk change is run will be able to change card type, (i.e. cards in any state including Lost, Stolen and Damaged can be changed, but not cards in a card state that is added manually by an operator.</li></ul></td></tr><tr><td>Change Activation Date</td><td>Check if the access start date needs to be changed. When checked, the date and time fields are enabled allowing you to select a new activation date.</td></tr><tr><td>Change Expiry Date</td><td>Check if the access end date needs to be changed. When checked, the date and time fields are enabled allowing you to select a new expiry date.</td></tr></tbody></table>

</details>

5. Click the **OK** button.

   The Change Card or Credential Details pop-up closes and your changes are saved.


---

# 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/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/card-or-credential-details-to-change-card.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.
