> 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/active-directory-dashboard.md).

# Active Directory dashboard

Configure Active Directory dashboard entries in Remote Desktop Manager, including the mode, host or LDAP path, domain, OU, LDAPS, port, and credentials.

This article details the settings and options available for ***Active Directory dashboard*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the session is displayed.</td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. Select a host mode from the list.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td><p>How Remote Desktop Manager locates the Active Directory domain. The fields shown in this tab depend on the selected mode:</p><ul><li><strong>Custom</strong></li><li><strong>LDAP</strong></li><li><strong>My domain</strong></li></ul></td></tr><tr><td><strong>Host</strong></td><td>The host name of the domain controller. Enter a host name or choose one from a list. Shown when <em><strong>Mode</strong></em> is set to <em><strong>Custom</strong></em>.</td></tr><tr><td><strong>Path</strong></td><td>The LDAP path of the directory. The path must start with <code>LDAP://</code> or <code>LDAPS://</code>. Shown when <em><strong>Mode</strong></em> is set to <em><strong>LDAP</strong></em>. Click the help button next to the field to open the Microsoft documentation on LDAP paths.</td></tr><tr><td><strong>Domain</strong></td><td>The Active Directory domain. Hidden when <em><strong>Mode</strong></em> is set to <em><strong>LDAP</strong></em>. Editable only when <em><strong>Mode</strong></em> is set to <em><strong>Custom</strong></em> and <em><strong>Credentials</strong></em> is set to <em><strong>Username and password</strong></em>.</td></tr><tr><td><strong>OU/Container DN</strong></td><td>The distinguished name of the organizational unit or container to open. Hidden when <em><strong>Mode</strong></em> is set to <em><strong>LDAP</strong></em>.</td></tr><tr><td><strong>Use LDAP over SSL</strong></td><td>Connect to the directory with LDAP over SSL (LDAPS).</td></tr><tr><td><strong>Port</strong></td><td>The port used to connect to the directory. The default port is 389, or 636 when <em><strong>Use LDAP over SSL</strong></em> is selected.</td></tr><tr><td><strong>Test connection</strong></td><td>Connect to the directory with the current settings and credentials to validate them. When an <em><strong>OU/Container DN</strong></em> is entered, the test also checks that it exists.</td></tr><tr><td><strong>Username</strong></td><td>The username used to connect to the directory. Available when <em><strong>Credentials</strong></em> is set to <em><strong>Username and password</strong></em>.</td></tr><tr><td><strong>Password</strong></td><td>The password used to connect to the directory. Available when <em><strong>Credentials</strong></em> is set to <em><strong>Username and password</strong></em>. This field is unavailable when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</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/rdm/knowledge-base/knowledge-base-articles/entry-settings/active-directory-dashboard.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.
