> 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/rdm/fr/concepts/basic-concepts/information.md).

# Information

Les entrées d'information dans Remote Desktop Manager centralisent les données non secrètes comme les clés de licence, les codes de porte et les procédures, pour une consultation rapide par l'équipe.

Une entrée d'information centralise les données d'affaires non secrètes telles que les clés de licence, les codes de porte ou les procédures que les équipes doivent consulter. Restreignez les personnes autorisées à modifier ou à consulter ces enregistrements à l'aide des permissions de dossier ou de coffre, et gardez-les près des sessions ou des actifs connexes pour un soutien plus rapide.

#### Voir aussi

* [Devolutions Academy - Managing Information Entries](https://academy.devolutions.net/student/path/1916054/activity/2667048)


---

# 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/rdm/fr/concepts/basic-concepts/information.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.