> 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/intermediate-concepts/playlists.md). # Playlists Launch grouped connections together with playlists in Remote Desktop Manager to automate daily routines, maintenance windows, and onboarding. Playlists automate recurring tasks by launching selected connections together, saving time and reducing clicks. In Remote Desktop Manager, you can create local, shared, or user vault playlists to open your standard connections in embedded mode with one action. This is ideal for routines like starting your daily toolset, preparing a maintenance window, or onboarding a client. For broader connection workflows, playlists complement centralized remote connection management. Enhance automation by pairing playlists with scripts and events to run pre- or post-connection tasks such as checks, logging, or notifications. #### Related topics * [Playlist](/rdm/ribbon-menu-bar/edit/playlist.md) * [Embedded sessions](/rdm/user-interface/content-area/embedded-sessions.md) #### See also * [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 dynamically 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/intermediate-concepts/playlists.md?ask=&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 `build a script that syncs our docs to a CMS` 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.