> 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/ribbon-menu-bar/edit/move.md).

# Flyt

Brug valgmuligheden Flyt i Remote Desktop Manager til at flytte en post til den rigtige gruppe eller mappe og undgå fejlplacerede poster.

Hvis De vil flytte en post under en anden gruppe eller mappe i Remote Desktop Manager, kan De vælge posten med musen og flytte den under den rigtige gruppe eller mappe, men for at undgå lette fejl og flytte den under den forkerte gruppe anbefaler vi på det kraftigste at bruge valgmuligheden ***Flyt***.

1. Vælg posten i navigationsruden, og brug derefter menuen ***Rediger*** – ***Flyt***.
2. Vælg den mappe eller gruppe, som De vil flytte posten under, og klik derefter på ***Vælg***.


---

# 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/ribbon-menu-bar/edit/move.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.