> 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/enable-temporary-access.md).

# Enable temporary access

Enable temporary access in Remote Desktop Manager to grant a user time limited entry permissions without permanently changing access rights.

With the ***Temporary Access*** feature, you can provide a designated user with temporary access to an entry during a designated time frame. This is much more secure than changing the user’s access rights and then changing them back once the task is done.

{% hint style="warning" %}
These settings are only available for the Devolutions Server, Microsoft SQL Server, and Microsoft Azure SQL advanced workspaces.
{% endhint %}

### Global Temporary Access Settings

***Temporary Access*** is set to ***Denied*** by default in Remote Desktop Manager.

1. To enable the feature, go to ***Administration – Vault Settings – Security Settings – Temporary Access***.
2. Set the ***Mode*** to ***Allowed***.
3. Optional: Change the ***Authorizers*** to ***Custom*** to add users to the authorizers list.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>By default, only administrators can authorize temporary access requests.</p></div>
4. Click ***OK***.

### Granular Temporary Access Settings

***Temporary Access*** can also be granulary set on each entry and folder.

1. Open the ***Properties*** of your entry or folder.
2. Go to ***Security Settings – Temporary Access***.
3. Select a ***Mode***. By default, the ***Mode*** is set to inherit the settings from the ***Root***. You can choose to inherit from another folder, allow, or even deny the temporary access of this entry or folder.
4. Select ***Authorizers***. By default, ***Authorizers*** are set to inherit the settings from the ***Root***. You can choose to inherit from another folder, allow authorization by administrators only, or customize and add users to the list of this entry or folder.
5. Click ***OK***.


---

# 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/enable-temporary-access.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.
