> 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/add-elevated-credentials-to-session-entries.md).

# Add elevated credentials to session entries

Add elevated credentials to Remote Desktop Manager session entries and use variables or typing functions to authenticate with alternate accounts.

Session entries in Remote Desktop Manager support alternative credentials that can be used instead of the ones set in the ***General*** tab in ***Common*** – ***General***. To configure these alternate credentials, head over to the entry's ***Properties*** – ***Connection*** – ***Alternate***, and choose a credential mode from the ***Credentials*** dropdown menu in the ***Elevated credentials*** section.

{% hint style="info" %}
Alternate credentials have their own variables, namely `$ELEVATED_USERNAME$` and `$ELEVATED_PASSWORD$`.Remember to enable the ***Allow password in variable***option, located in ***Administration*** – ***System settings*** – ***Password policy***,\*\*\*\*to use the latter variable.
{% endhint %}

To launch a session using elevated credentials, right-click on the entry, then click on ***Open with parameter*** – ***Open using elevated credentials***.

{% hint style="info" %}
Once configured, an entry's elevated credentials can be typed automatically in an opened session using the ***Type elevated username***, ***Type elevated domain***, or ***Type elevation password*** functions.
{% endhint %}

#### SSH Terminal-specific elevation settings

***SSH Terminal*** session entries boast specific elevation settings, which can be used to leverage particular ***Elevation modes*** and ***Elevation tools*** to connect to different operating systems.

These allow, for example, to automatically log on to Linux servers using ***Su*** as an ***Elevation tool***.


---

# 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/add-elevated-credentials-to-session-entries.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.