> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/removing-a-card-or-credential.md).

# Removing a card or credential

An operator can remove a card or mobile credential, as follows.

To remove cards or mobile credentials in bulk, see [Creating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change.md).

1. Click on the card or mobile credential you want to remove from the Cardholder.
2. Click the **Remove** button.

   The Remove Card pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-912213b911df5b7b9da813de2d10389afbec44b7%2Fcardholdercards_removecardpopup.png?alt=media)
3. Select the appropriate card state for card history, (e.g. Lost, Damaged, etc.) from the **Change Reason (Card Status)** drop-down of available card states.
4. Click the **OK** button.

   The Remove Card pop-up closes and the card or mobile credential disappears from the list of cards on the Cardholder Cards tile.

   **Note:** If you decide to cancel this change, the **Revert to Saved** button allows you to do so before saving it.
5. Click the **Save** button.


---

# 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/removing-a-card-or-credential.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.
