> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/fr/web-interface/vaults/entries/entry-section/documentation.md).

# Documentation

L'onglet Documentation d'une entrée Devolutions Server stocke l'information connexe sous forme de pages Markdown ou WYSIWYG, chiffrées dans les espaces de travail Server et Cloud.

La fonctionnalité ***Documentation*** permet de stocker de l'information concernant les entrées.

{% hint style="info" %}
Cette fonctionnalité est aussi disponible avec les espaces de travail Devolutions Cloud et SQL Server.

La fonctionnalité ***Documentation*** est chiffrée uniquement pour les espaces de travail Devolutions Server et Devolutions Cloud. Si vous utilisez des espaces de travail comme SQL Server ou Azure SQL, la fonctionnalité ***Documentation*** n'est pas chiffrée.
{% endhint %}

#### Ajouter une nouvelle page

1. Choisissez l'entrée et sélectionnez ***Documentation***.
2. Cliquez sur ***Ajouter***.
3. ***Nommez*** le document avec un titre.
4. Saisissez le texte en utilisant ***Markdown*** ou ***WYSIWYG***.
5. Cliquez sur ***Enregistrer*** pour créer votre page de documentation.


---

# 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://docs.devolutions.net/server/fr/web-interface/vaults/entries/entry-section/documentation.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.