> 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/concepts/basic-concepts/documents-and-attachments.md).

# Documents et pièces jointes

Les documents et pièces jointes dans Devolutions Server stockent des fichiers ou des notes autonomes sous forme d'entrées de document et lient des fichiers complémentaires à n'importe quelle entrée de

Les documents et pièces jointes dans Devolutions Server regroupent les fichiers connexes et la documentation de référence avec les entrées sécurisées qui les utilisent. Une entrée de document stocke un fichier autonome ou une note enrichie dans un coffre, tandis que la section Pièces jointes vous permet de lier des fichiers directement à tout type d'entrée (session, identifiant, information, etc.). Les deux sont stockés de façon centralisée, bénéficient d'un historique et sont protégés par les mêmes permissions et la même piste d'audit que leurs entrées parentes.

#### Sujets connexes

* [Pièces jointes](/server/fr/web-interface/vaults/entries/entry-section/attachments.md)
* [Documentation](/server/fr/web-interface/vaults/entries/entry-section/documentation.md)
* [Créer des entrées manuellement](/server/fr/web-interface/vaults/entries/create-entries-manually.md)


---

# 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/concepts/basic-concepts/documents-and-attachments.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.