> 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/intermediate-concepts/playlists.md).

# Playlists

Starten Sie gruppierte Verbindungen gemeinsam mit Playlists in Remote Desktop Manager, um tägliche Routinen, Wartungsfenster und Onboarding zu automatisieren.

Playlists automatisieren wiederkehrende Aufgaben, indem sie ausgewählte Verbindungen gemeinsam starten, was Zeit spart und Klicks reduziert.

In Remote Desktop Manager können Sie lokale, geteilte oder Benutzer-Tresor-Playlists erstellen, um Ihre Standardverbindungen mit einer Aktion im eingebetteten Modus zu öffnen. Das ist ideal für Routinen wie das Starten Ihres täglichen Werkzeugsatzes, das Vorbereiten eines Wartungsfensters oder das Onboarding eines Kunden. Für umfassendere Verbindungsworkflows ergänzen Playlists die zentralisierte Remote-Verbindungsverwaltung.

Verbessern Sie die Automatisierung, indem Sie Playlists mit Skripten und Ereignissen kombinieren, um Aufgaben vor oder nach der Verbindung auszuführen, etwa Prüfungen, Protokollierung oder Benachrichtigungen.

#### Verwandte Themen

* [Playlist](/rdm/de/ribbon-menu-bar/edit/playlist.md)
* [Eingebettete Sitzungen](/rdm/de/user-interface/content-area/embedded-sessions.md)

#### Siehe auch

* [Devolutions Academy - Automating Connections with Playlists](https://academy.devolutions.net/student/path/1925039/activity/2667188)
* [Devolutions Blog - The Basics: Remote Desktop Manager Playlist](https://blog.devolutions.net/2018/08/the-basics-remote-desktop-manager-play-list/)


---

# 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/intermediate-concepts/playlists.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.
