> 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/knowledge-base-articles/entry-settings/common-settings/alternate.md).

# Alternate

Set alternate hosts, elevated credentials and SSH elevation settings for a session entry in Remote Desktop Manager.

The ***Alternate*** section of a session entry defines other hosts to connect to when the main host is not available, and the alternate (elevated) credentials of the entry. For SSH terminal entries, it also defines how the shell is elevated.

Available for session and VPN entries. In the entry properties, select ***Connection*** – ***Alternate***. The ***Alternate host*** and ***Credentials*** groups are not shown for playlists. Not available on macOS. By default, the section is hidden in the simplified view of the properties; select ***Show all properties*** to display it.

### Alternate host

The list at the top of the group defines how Remote Desktop Manager chooses the host when the session opens:

* ***None***: uses the host of the entry. The list of alternate hosts is disabled. This is the default value.
* ***Ping***: pings the host of the entry, then the alternate hosts in order, and connects to the first one that answers.
* ***Prompt***: asks the user to select a host among the host of the entry and the alternate hosts.
* ***Manual***: uses the host of the entry. To connect to an alternate host, open the entry with the ***Open (prompt for host)*** command.
* ***Port scan***: scans the port of the host of the entry, then of the alternate hosts in order, and connects to the first one that answers.

When alternate hosts are set, the ***Open (prompt for host)*** command is offered for the entry with every mode.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Allow custom host</strong></em></td><td>Lets the user type a host that is not in the list. Shown with the <em><strong>Prompt</strong></em> mode.</td></tr><tr><td><em><strong>Open VPN before</strong></em></td><td>Opens the VPN, tunnel or gateway of the entry before testing or offering the alternate hosts. Not shown when the entry uses the <em><strong>Devolutions Gateway</strong></em> type in <em><strong>Connection</strong></em> – <a href="https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/vpn-tunnel-gateway.md"><em><strong>VPN/tunnel/gateway</strong></em></a>.</td></tr><tr><td><em><strong>Alternate hosts</strong></em></td><td>List of alternate hosts, one per line. A host can include a port, such as <code>server2:3390</code>, and variables. The <em><strong>Add host</strong></em> button selects a host from the network; it is disabled when network scans are disabled by policy.</td></tr></tbody></table>

### Credentials

Alternate credentials replace the credentials of the entry when the session is opened with elevated credentials, and they provide the values of the `$ELEVATED_USERNAME$`, `$ELEVATED_PASSWORD$` and `$ELEVATED_DOMAIN$` variables and of the ***Type elevated*** commands. See [Add elevated credentials to session entries](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/add-elevated-credentials-to-session-entries.md).

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Credentials</strong></em></td><td><p>Source of the alternate credentials. The fields shown under the list depend on the source:</p><ul><li><em><strong>None</strong></em>: no alternate credentials. This is the default value.</li><li><em><strong>Use session credentials</strong></em>: the credentials of the entry.</li><li><em><strong>Username and password</strong></em>: credentials entered in the entry.</li><li><em><strong>Linked</strong></em>: a credential entry of a vault. Select the vault in the <em><strong>Vault</strong></em> list, then select the entry. Selecting the user vault from an entry in a shared vault finds the credential entry by the name you enter, in each user's user vault. For entries in the user vault, the shared vaults are listed only when the <em><strong>Allow linking to shared vault credentials from the user vault</strong></em> system setting is enabled.</li><li><em><strong>My personal credentials</strong></em>: the personal credentials of the user.</li><li><em><strong>Inherited</strong></em>: the alternate credentials of the parent folder.</li><li><em><strong>My privileged account</strong></em>: the privileged account of the user.</li><li><em><strong>Privileged account</strong></em>: a PAM account. Offered with a Remote Desktop Manager PAM license, when the workspace supports PAM and the entry type supports PAM credentials.</li></ul></td></tr></tbody></table>

### Elevation settings

Shown for SSH terminal entries. These settings control the ***Elevate shell*** command of the terminal. When the user clicks it, Remote Desktop Manager types the elevation command (`sudo -i` or `su`, with the elevated username when it differs from the session username) and then the elevated password in the terminal. The shell is never elevated automatically when the session opens.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Elevation mode</strong></em></td><td>Defines whether the <em><strong>Elevate shell</strong></em> command is offered in the session: <em><strong>Automatic</strong></em> (offered; the user clicks it to elevate) or <em><strong>Manual</strong></em> (not offered; the user elevates the shell, for example with a post-login macro that sends <code>$ELEVATED_PASSWORD$</code>). The default value is <em><strong>Automatic</strong></em>.</td></tr><tr><td><em><strong>Elevation tool</strong></em></td><td>Command used to elevate the shell: <em><strong>Sudo</strong></em>, <em><strong>None</strong></em> or <em><strong>su</strong></em>. The default value is <em><strong>Sudo</strong></em>. With <em><strong>None</strong></em>, the <em><strong>Elevate shell</strong></em> command is not offered.</td></tr></tbody></table>

When all the settings of this section are left at their default values, the ***Elevate shell*** command is offered only if the entry has a password, and uses `sudo` with that password. When the alternate credentials have no password, the password of the entry is typed instead. The commands typed for each elevation tool are described in [Add elevated credentials to session entries](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/add-elevated-credentials-to-session-entries.md).

See also [Connect with su-user in SSH sessions](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/connect-with-su-user-in-ssh-sessions.md).


---

# 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/knowledge-base-articles/entry-settings/common-settings/alternate.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.
