> 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/generic-administration-tasks/history-notes-tab.md).

# History/Notes tab

All site items include a **History/Notes** tab in their Properties window. This tab displays the item’s creation date and time, who last modified the item's properties and when, and allows you to add any relevant notes about the item.

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

**Note:** The tabs that display alongside the **History/Notes** tab will differ depending on the site item. This example is for a Schedule.

1. Enter any note(s) you want to record in the **Notes** field.

   **Notes:**

   * The **Notes** field accepts at least 2,500 characters.
   * The scroll bar can be used to move through the text, or the normal navigation keys can be used, (i.e. Up and Down Arrows, Page Up and Down, and Home and End).
   * **Right clicking** anywhere in the **Notes** field will display a context menu with the following options:

     <table><thead><tr><th width="90">Option</th><th width="380">Description</th><th>Short-cut</th></tr></thead><tbody><tr><td>Revert</td><td>Text can be removed by clicking this prior to clicking <strong>OK</strong> or <strong>Apply</strong>.</td><td>Ctrl-Z</td></tr><tr><td>Cut</td><td>Only enabled when text is selected. The selected text can be cut to the Windows clipboard.</td><td>Ctrl-X</td></tr><tr><td>Copy</td><td>Only enabled when text is selected. The selected text can be copied to the Windows clipboard.</td><td>Ctrl-C</td></tr><tr><td>Paste</td><td>Only enabled when the Windows clipboard contains text, (i.e. text has already been cut or copied). The text can be pasted from the Windows clipboard to the current text-edit cursor position.</td><td>Ctrl-V</td></tr><tr><td>Delete</td><td>Only enabled when text is selected. The selected text will be deleted if clicked.</td><td></td></tr><tr><td>Select All</td><td>Only enabled when <strong>no</strong> text is selected. Clicking it will select all the text in the <strong>Notes</strong> field.</td><td></td></tr></tbody></table>
2. The **History** grid is "read-only" and shows Audit history details for the item.

   Each entry represents one change made to the item. The entries are sorted by time, in descending order, with the latest change at the top.

   **Note:** Extra details can be revealed for an entry by selecting (highlighting) an entry.


---

# 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/generic-administration-tasks/history-notes-tab.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.
