> 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/concepts/intermediate-concepts/override-settings.md).

# Override settings

Override specific entry settings in Remote Desktop Manager without duplicating entries, applying context-specific changes while keeping vaults tidy.

Override the configuration of specific settings without permanently changing existing entries. Rather than duplicating an entry to change a single value, overrides let you reuse the same entry with your customizations, keeping the workspace tidy while preserving the original configuration.

In Remote Desktop Manager, overrides provide day-to-day flexibility for administrators: apply context-specific changes at launch or for a task, then continue using the shared entry as-is for everyone else. This helps standardize configurations while reducing clutter and maintenance effort.

#### Related topics

* [Inheritance](/rdm/knowledge-base/knowledge-base-articles/inheritance-in-remote-desktop-manager.md)
* [User-specific settings](/rdm/ribbon-menu-bar/edit/batch-edit.md#batch-edit-options)
* [Local Specific Settings](/rdm/ribbon-menu-bar/edit/batch-edit.md#batch-edit-options)

#### See also

* [Devolutions Academy - Customizing Entries with Specific Settings](https://academy.devolutions.net/student/path/1925039/activity/2667191)


---

# 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/concepts/intermediate-concepts/override-settings.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.