> 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/knowledge-base/how-to-articles/change-sorting-priority.md).

# Change sorting priority

Adjust entry and folder sorting priority in Remote Desktop Manager to organize your navigation pane based on custom priority values.

The sort priority of an entry or a folder sets its position among the entries of the same level in the navigation pane. The default value is 0. A higher value places the entry before the others. The value ranges from -1000 to 100000.

1. Right-click an entry or a folder and select ***Properties***.
2. Go to ***Common*** – ***User interface***.
3. In the ***Tree*** group, enter a value in ***Sort priority***.
4. Click ***Save***.

On Windows and Linux, to change the sort priority of several entries at once, select them, right-click the selection, then select ***Edit*** – ***Sort priority***.

The other settings of this section are detailed in [User interface](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/user-interface.md).


---

# 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/knowledge-base/how-to-articles/change-sorting-priority.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.
