> 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/knowledge-base-articles/local-color-coding.md).

# Local color coding

Set up local color coding in Remote Desktop Manager to categorize entries with custom colors for faster navigation and identification.

Remote Desktop Manager allows users to mark entries using colored categories. These categories help classify entries at a glance, improving navigation and identification.

Select an entry and click ***Edit*** – ***Local color coding*** – ***Manage***.

{% hint style="info" %}
Applying ***Local color coding*** to a local workspace or folder causes all entries within it to inherit the colored category.
{% endhint %}

| SETTINGS               | DESCRIPTIONS                                                                                      |
| ---------------------- | ------------------------------------------------------------------------------------------------- |
| **Add a category**     | Create a new category and assign a custom color (custom or web).                                  |
| **Remove a category**  | Delete the category.                                                                              |
| **Edit a category**    | Select a category to change the color using the color drop-down list or modify the category name. |
| **Reorder a category** | Click the up/down arrow buttons to adjust the order of categories.                                |


---

# 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/knowledge-base-articles/local-color-coding.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.