> 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/add-ons.md).

# Add-ons

Add-ons extend Remote Desktop Manager with optional entry types, tools, and integrations to tailor the platform to your environment and stack.

Add-ons extend Remote Desktop Manager with optional entry types, tools, and integrations so the platform can be tailored to your stack. They let you add capabilities such as new connection technologies, external utilities, or credential and workspace providers without changing your core configuration.

Use add-ons to streamline remote workflows, integrate specialized admin tools, and support vendor-specific systems while maintaining consistent security, auditing, and organization.

#### Related topics

* [Tools tab](/rdm/ribbon-menu-bar/tools.md)

#### See also

* [Devolutions Academy - Using Add-Ons](https://academy.devolutions.net/student/path/1916054/activity/2667049)
* [Devolutions Blog - Remote Desktop Manager Add-on Manager](https://blog.devolutions.net/2019/06/improved-feature-rdm-add-on-manager/)


---

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