> 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/delinea-server-pam.md).

# Delinea Server PAM

Configure the Delinea Server PAM credential entry in Remote Desktop Manager, including the tenant URL, login credentials, and account selection.

This article details the many settings and options available for ***Delinea Server PAM*** credential entries in Remote Desktop Manager.

{% hint style="info" %}
This entry requires a valid license. Without one, the entry displays a ***License key is required*** warning and its settings cannot be edited.
{% endhint %}

<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></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Tenant URL</strong></td><td>Enter the URL of the Delinea Server PAM tenant. This field is required.</td></tr><tr><td><strong>Use "My account settings"</strong></td><td>Use the Delinea Server PAM username and password saved in <em><strong>File</strong></em> – <em><strong>My account settings</strong></em> instead of the ones entered in this entry. When enabled, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields are disabled. This option is not displayed when a policy disables <em><strong>My account settings</strong></em>.</td></tr><tr><td><strong>Username</strong></td><td>Enter the username used to authenticate to the tenant. This field is required unless <em><strong>Use "My account settings"</strong></em> is enabled.</td></tr><tr><td><strong>Password</strong></td><td>Enter the password used to authenticate to the tenant. This field is disabled when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr><tr><td><strong>Account</strong></td><td>The account whose credentials the entry retrieves. Click the browse button to authenticate to the tenant and select an account from the list. This field is required unless <em><strong>Always prompt with list</strong></em> is enabled. When that option is enabled, the field is disabled and the browse button is hidden.</td></tr><tr><td><strong>Always prompt with list</strong></td><td>Prompt with the list of available accounts each time the entry is used, instead of always using the same <em><strong>Account</strong></em>.</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/delinea-server-pam.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.
