> 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/web-interface/administration/user-and-security-management/reset-server-cache.md).

# Reset server cache

Reset the Server Cache in Devolutions Server for entries, users, roles, vaults, domain, or Microsoft Authentication data pulled from the database.

***Reset Server Cache*** for specific elements.

### Reset server cache

<table><thead><tr><th width="252">Option</th><th>Description</th></tr></thead><tbody><tr><td><ul><li><em><strong>Entries</strong></em></li><li><em><strong>Users</strong></em></li><li><em><strong>Rôles</strong></em></li><li><em><strong>Vaults</strong></em></li></ul></td><td>When selecting one of those options, when resetting the cache, it will pull back all the information from the database and put the information in the server's memory cache.</td></tr><tr><td><ul><li><em><strong>Domain</strong></em></li><li><em><strong>Microsoft Authentication</strong></em></li></ul></td><td>When resetting the Domain or the Microsoft Authentication cache, it will wipe out the information saved in the database and will reload all the users and groups memberships pulled from Active Directory or from Entra ID.</td></tr></tbody></table>


---

# 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/web-interface/administration/user-and-security-management/reset-server-cache.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.
