> 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/documentation/fr/modules/tabs/notes.md).

# Notes

L'onglet *Notes* fournit un champ de texte libre pour stocker des informations supplémentaires. Les notes sont affichées dans l'ordre de leur création. Vous pouvez également ajouter un document

## Ajouter une note

* Pour ajouter une note, cliquez sur **+Ajouter**
* Vous pouvez ajouter du texte et le formater selon vos besoins
* Vous pouvez ajouter un document à cette note

## Supprimer une note

* Pour supprimer une note, vous devez cliquer sur **supprimer**
* Vous pouvez supprimer uniquement la pièce jointe en cliquant sur supprimer (l'option apparaît lorsque vous déplacez votre souris sur la pièce jointe)

{% hint style="success" %}
Lorsque vous supprimez une pièce jointe, elle n'est pas complètement supprimée, vous pouvez la retrouver dans **Gestion** > **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/documentation/fr/modules/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.