> 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-notes-tile-actions.md).

# Cardholder Notes Tile actions

This tile displays all notes captured to date for that Cardholder. Operators who are authorised to edit the notes, can add to, update or delete previously captured details. The ability for an Operator to view and/or edit notes for the Cardholder will depend on their privileges.

### Operator Privileges

<table><thead><tr><th width="208">To...</th><th>you need...</th></tr></thead><tbody><tr><td><strong>view</strong> Cardholder notes,</td><td>either the "View Cardholder Notes" OR "Edit Cardholder Notes" privilege in the division of the cardholder.<br><br><strong>Note:</strong> In the event that you do not have the privileges required to view the notes, the following message will display in the tile:<br><em>"You are not authorised to view this content. Please contact your Administrator"</em></td></tr><tr><td><strong>edit</strong> Cardholder notes,</td><td>"Edit Cardholder Notes" privilege in the division of the cardholder.</td></tr><tr><td><strong>add</strong> Cardholder notes,</td><td>the "Add Cardholder Note" privilege.<br><br><strong>Note:</strong> This privilege does not allow you to delete Cardholder notes.</td></tr></tbody></table>


---

# 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-notes-tile-actions.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.
