> 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

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](https://docs.devolutions.net/rdm/commands/edit/play-list/)
* [Embedded sessions](https://docs.devolutions.net/rdm/user-interface/content-area/embedded-sessions/)

#### 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 current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/concepts/intermediate-concepts/playlists.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.