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

# Documents and attachments

Documents and attachments in Remote Desktop Manager let you store files alongside entries, keeping runbooks and license files in context and secure.

Documents and attachments let you store files alongside entries so critical information travel with the connection, credential, or asset. Attach runbooks, diagrams, license files, or exports to keep everything in context and controllable through folder or vault permissions. Upload files manually, link external documents, or manage them in bulk with import tools.

#### Related topics

* [Attachments](/rdm/ribbon-menu-bar/window/attachments.md)

#### See also

* [Devolutions Academy – Breaking down common scenarios: automated asset and inventory tracking](https://academy.devolutions.net/student/activity/3380802)
* [Devolutions Academy - Managing Documentation and Attachments](https://academy.devolutions.net/student/path/1916054/activity/2667047)
* [Devolutions Academy – Must-know features to boost productivity](https://academy.devolutions.net/student/activity/3266674)


---

# 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/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.