> 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/salesforce-cloud.md).

# Salesforce Cloud

Configure Salesforce Cloud dashboard entries in Remote Desktop Manager, including the flow type, login URL, callback URL, client ID, and security token.

This article details the many settings and options available for ***Salesforce Cloud*** dashboard entries in Remote Desktop Manager. The dashboard lets you search, filter, and open Salesforce cases, and create threads and messages from 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. A folder can be selected by clicking the arrow or the three dots to open the <em><strong>Folder</strong></em> window. To create a new folder, click on the plus (<strong>+</strong>) icon.</td></tr><tr><td><strong>Display</strong></td><td>How the dashboard is displayed: <em><strong>Default</strong></em> follows the display mode of the nearest parent folder that sets one, otherwise the default for the entry type. <em><strong>Embedded (tabbed)</strong></em> opens it in a tab of the main window, and <em><strong>Undocked</strong></em> opens it in a separate window.</td></tr><tr><td><strong>Credentials</strong></td><td>Where the Salesforce username and user password come from. When the credentials are taken from another source, such as a linked credential entry, the <em><strong>Username</strong></em> and <em><strong>User password</strong></em> fields of the <em><strong>General</strong></em> section are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Flow type</strong></td><td><p>The OAuth flow used to authenticate to Salesforce:</p><ul><li><strong>Username password flow</strong> — Authenticates with the client ID, client secret, username, user password, and security token. This is the default value.</li><li><strong>Web server flow with PKCE</strong> — Opens your browser to sign in to Salesforce, then returns to Remote Desktop Manager through the callback URL.</li></ul></td></tr><tr><td><strong>Login URL</strong></td><td>The Salesforce URL used to authenticate. The default value is <code>https://login.salesforce.com/services/oauth2/token</code>. With the <em><strong>Web server flow with PKCE</strong></em>, enter your Salesforce domain URL, for example <code>https://mydomain.my.salesforce.com</code>. Required.</td></tr><tr><td><strong>Callback URL</strong></td><td>The callback URL registered in your Salesforce app, for example <code>http://localhost:17171/callback/</code>. Only enabled and required with the <em><strong>Web server flow with PKCE</strong></em>. See <a href="#callback-url-requirements">Callback URL requirements</a>.</td></tr><tr><td><strong>Client ID</strong></td><td>The <em><strong>Consumer Key</strong></em> of your Salesforce app. See <a href="#create-the-salesforce-app">Create the Salesforce app</a>. Required.</td></tr><tr><td><strong>Client Secret</strong></td><td>The <em><strong>Consumer Secret</strong></em> of your Salesforce app. Only enabled and required with the <em><strong>Username password flow</strong></em>. The saved value cannot be revealed in the field.</td></tr><tr><td><strong>Username</strong></td><td>Your Salesforce username. Only enabled and required with the <em><strong>Username password flow</strong></em>, when the credentials are not taken from another source.</td></tr><tr><td><strong>User password</strong></td><td>Your Salesforce password. Only enabled and required with the <em><strong>Username password flow</strong></em>, when the credentials are not taken from another source. Disabled when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr><tr><td><strong>Security token</strong></td><td>Your Salesforce security token. Only enabled and required with the <em><strong>Username password flow</strong></em>.</td></tr></tbody></table>

### Create the Salesforce app

The ***Client ID*** comes from an app registered in Salesforce. Since the Salesforce Spring '26 release, new Salesforce orgs cannot create Connected Apps and must use External Client Apps instead. An External Client App provides the consumer key, callback URL, and PKCE support that the ***Salesforce Cloud*** entry needs.

{% hint style="info" %}
An existing Connected App can still be used. Make sure its OAuth settings follow the same rules as below (callback URL, OAuth scopes, and PKCE), then copy its consumer key into the ***Client ID*** field.
{% endhint %}

1. In Salesforce ***Setup***, enter "External Client" in the ***Quick Find*** box, then select ***External Client App Manager***.
2. Click ***New External Client App***.
3. Fill in the ***Basic Information*** section, including the app name and a contact email.
4. Expand the ***API (Enable OAuth Settings)*** section and check ***Enable OAuth***.
5. In ***Callback URL***, enter the callback URL that you will also enter in the entry, for example `http://localhost:17171/callback/`. See [Callback URL requirements](#callback-url-requirements).
6. In ***OAuth Scopes***, add ***Manage user data via APIs (api)***, ***Perform requests at any time (refresh\_token, offline\_access)***, and ***Access unique user identifiers (openid)***.
7. In the security settings, check ***Require Proof Key for Code Exchange (PKCE) extension for Supported Authorization Flows***, and uncheck ***Require secret for Web Server Flow***.
8. Click ***Create***.
9. Open the app, go to the ***Settings*** tab, expand ***OAuth Settings***, then click ***Consumer Key and Secret***. Salesforce may ask you to verify your identity.
10. Copy the ***Consumer Key*** and paste it in the ***Client ID*** field of the entry.

### Callback URL requirements

With the ***Web server flow with PKCE***, the callback URL must:

* Point to a loopback address: `localhost`, `127.0.0.1`, or `[::1]`.
* End with a slash (`/`), for example `http://localhost:17171/callback/`.
* Be identical in Remote Desktop Manager and in the Salesforce app. Copy and paste it instead of typing it.

When the dashboard authenticates, Remote Desktop Manager displays an error message if the callback URL does not follow these rules.


---

# 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/salesforce-cloud.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.