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

# Afspilningslister

Afspilningslister i Devolutions Cloud lader Remote Desktop Manager starte sekvenser af gemte VPN-, RDP- og SSH-sessioner med centralt administrerede legitimationsoplysninger fra bokse.

Afspilningslister samler flere forbindelser eller værktøjer i sekvenser, der kan genbruges, så De kan starte flere relaterede handlinger med én enkelt kommando. Listerne mindsker gentagne klik, når De altid åbner det samme sæt sessioner til det daglige arbejde, vedligeholdelsesvinduer eller onboarding af kunder.

Med Devolutions Cloud som arbejdsområde kan afspilningslister i Remote Desktop Manager pege på poster, der er gemt i bokse i Devolutions Cloud, og dermed kombinere centraliseret opbevaring af adgangskoder med fleksible startarbejdsflows på klientsiden. En afspilningsliste kan for eksempel åbne en VPN, der er gemt i Devolutions Cloud, og derefter flere RDP- og SSH-sessioner, som alle bruger legitimationsoplysninger fra Devolutions Cloud.

#### Relateret emne

* [Afspilningslister](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/playlists)


---

# 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/cloud/da/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.