> 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/da/user-interface/content-area/embedded-sessions.md).

# Integrerede sessioner

Lær, hvordan indlejrede sessioner i Remote Desktop Manager lader Dem åbne flere sessioner på faner og arrangere dem ved hjælp af visninger med opdelte vinduer.

{% embed url="<https://youtu.be/FtSlp_TVAxE?t=759>" %}

Visningstilstanden ***Integreret (faner)*** giver Dem mulighed for at åbne flere sessioner som faner i Remote Desktop Manager, på samme måde som fanerne i Deres almindelige webbrowser. ***Indlejrede sessioner*** er en af de tilgængelige visningstilstande, og de andre er ***Ekstern*** og ***Fradocket***.

#### Opdelte vinduer

I en indlejret session i Remote Desktop Manager er der mulighed for at vise flere vinduer med faner på samme tid. Som illustreret nedenfor skal De vælge en fane, holde den nede og trække den mod midten af skærmen for at få adgang til den firesidede retningskontrol. Ret retningskontrollen for at forankre fanen øverst, nederst, til venstre eller til højre for den tilstødende fane.


---

# 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/da/user-interface/content-area/embedded-sessions.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.