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

# Override settings

Override settings in Devolutions Server let administrators change values such as timeouts or security prompts for a specific vault or entry.

Override settings in Devolutions Server let you change configuration values for specific scopes without modifying the underlying system defaults. You can override options such as connection timeouts, display preferences, or security prompts for a particular vault, folder, or entry when its requirements differ from the global configuration.

This layered approach makes it easier to roll out standard policies while still accommodating exceptions. For instance, you might enforce strong confirmation prompts and shorter timeouts for production servers by overriding settings on their folder, without impacting less critical lab environments.

#### Related topics

* [System settings](/server/web-interface/administration/configuration/system-settings.md)

#### See also

* [Override settings](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/override-settings)


---

# 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/server/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.