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

# Add-ons

Add-ons erweitern Remote Desktop Manager um optionale Eintragstypen, Werkzeuge und Integrationen, um die Plattform an Ihre Umgebung und Ihren Technologie-Stack anzupassen.

Add-ons erweitern Remote Desktop Manager um optionale Eintragstypen, Werkzeuge und Integrationen, sodass die Plattform an Ihren Technologie-Stack angepasst werden kann. Sie ermöglichen es Ihnen, Funktionen wie neue Verbindungstechnologien, externe Dienstprogramme oder Anbieter von Anmeldeinformationen und Datenquellen hinzuzufügen, ohne Ihre Kernkonfiguration zu ändern.

Verwenden Sie Add-ons, um Remote-Workflows zu optimieren, spezialisierte Administrationswerkzeuge zu integrieren und herstellerspezifische Systeme zu unterstützen, während Sie durchgängige Sicherheit, Auditing und Organisation beibehalten.

#### Verwandte Themen

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

#### Siehe auch

* [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/de/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.