> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/glpi-12/tabs/notes.md).

# Notes

The *Notes* tab provides a free text field for storing additional information. Notes are displayed in the order of their creation. You can also add a document

<figure><img src="https://content.gitbook.com/content/uys4bnfAs7Oe2yWUUh3p/blobs/aDFvUA3pFKFMM8n5Qcwu/notes.png" alt=""><figcaption><p>Example of note</p></figcaption></figure>

## Add a note

* To add a note, click on **+Add**
* You can add text and format it to suit your needs
* You can add a document to this note

<figure><img src="https://content.gitbook.com/content/uys4bnfAs7Oe2yWUUh3p/blobs/MszeZC1whzhxnhddXyXY/notes-add.png" alt=""><figcaption><p>Add your note</p></figcaption></figure>

***

## Delete a note

* To delete a note, you need to click on **delete**
* You can delete only the attachment by clicking on delete (the option appears when you move your mouse over the attachment)

<figure><img src="https://content.gitbook.com/content/uys4bnfAs7Oe2yWUUh3p/blobs/PmVhixpiCLXGCiWdN0yI/notes-delete.png" alt=""><figcaption><p>Delete the note</p></figcaption></figure>

{% hint style="success" %}
When you delete an attachment, it is not completely deleted, you can find it in **`Management`** > **`Documents`**
{% endhint %}


---

# 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.glpi-project.org/glpi-12/tabs/notes.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.
