> 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/viewing-additional-card-or-credential-information.md).

# Viewing additional card or credential information

Cardholder card or mobile credential information that is not used on a regular basis is hidden in the normal view of the card list. To display this information, click on the arrow head to the left of the card or mobile credential you want to see the details for. This results in a second line appearing with the hidden information as shown below:

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

If you have the "View Mobile Credential Email and Mobile" privilege (see [Configuring Privileges for an Operator Group](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/operator-groups/configuring-privileges-for-an-operator-group.md)), you will be able to see the email address and mobile number that credentials were last sent to. This will also appear in the Cardholder History tile. If you do not have this privilege, the last used email address and mobile number fields will be blank in the Cardholder Cards tile, and absent from the Cardholder History tile.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6c88bb23617758edf1372da15a8806f3fa8189ee%2Fcardholdercards_cardinfo3.png?alt=media)


---

# 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/viewing-additional-card-or-credential-information.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.
