# How to configure the Salesforce integration

**URL:** <https://meta.discourse.org/t/how-to-configure-the-salesforce-integration/417136>\
**Category:** Integrations\
**Tags:** salesforce, how-to, platforms\
**Created:** [12 בנובמבר,‏ 2026,‏ 6:59pm UTC](https://meta.discourse.org/t/how-to-configure-the-salesforce-integration/417136 "2026-11-12T18:59:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)\
**Post date:** [12 בנובמבר,‏ 2026,‏ 6:59pm UTC](https://meta.discourse.org/t/how-to-configure-the-salesforce-integration/417136/1 "2026-11-12T18:59:57Z")

</div>

> 🔖 This guide covers the configuration steps required to connect Discourse to Salesforce using the [Discourse Salesforce](https://meta.discourse.org/t/discourse-salesforce/218267) plugin.
> 
> :discourse: [Discourse Salesforce](https://meta.discourse.org/t/discourse-salesforce/218267) is available on the Enterprise plan.
> 
> 🙋 Required user level: Administrator

## Step 0: Finding the right people in your organization

Before doing anything in Discourse, first make sure that you know the right people to involve from your organization to handle what’s required on the Salesforce side.

### Salesforce administrator

**Who they are:** In most organizations, this is typically whomever your team calls “the Salesforce admin” — the person who manages your Salesforce org’s configuration, not necessarily your IT system administrator.

**What they do:** Handles the initial setup on the Salesforce side by creating the External Client App (or Connected App) in Salesforce Setup, configuring OAuth settings, and retrieving the Consumer Key and Consumer Secret.

**What they need:** Access to Salesforce **Setup** and specifically the **External Client App Manager**. In Salesforce, this requires the **Customize Application** system permission. This is included in the standard **System Administrator** profile. If the person doing the setup doesn’t have a System Administrator profile, a Salesforce administrator will need to grant them a permission set that includes “Customize Application.”

### Salesforce integration user

**Who they are:** A Salesforce user whose account credentials are used by the Discourse plugin to make API calls to Salesforce.

**What they do:** Provides the username to go into the **salesforce username** setting in the Discourse Salesforce settings to facilitate all the API calls from Discourse to Salesforce.

**What they need:** This user must have:

| Permission | Why it’s needed |
| --- | --- |
| **API Enabled** | Required for any Salesforce API access |
| **Create, Read, Edit on Lead** | Create and link Leads from Discourse users |
| **Create, Read, Edit on Contact** | Create and link Contacts from Discourse users |
| **Create, Read, Edit on Case** | Create Cases from Discourse topics |
| **Create on Case Comment** | Sync topic replies as Case Comments |
| **Create on FeedItem** **(Chatter)** | Post topic activity to Chatter |

> **Note** : The Salesforce integration user can be the same person as the Salesforce administrator. However, as a security best practice, we recommend using a separate, more narrowly-permissioned account for the integration user.

## Step 1: Generate a certificate and private key

> **Role:** Discourse admin

Discourse Salesforce uses JWT Bearer Flow to authenticate with Salesforce. This requires an RSA key pair: a **public certificate** that Salesforce uses to verify the plugin’s identity and a **private key** that Discourse uses to sign its requests.

1. Follow [these instructions](https://developer.salesforce.com/docs/platform/sfdx-dev/guide/sfdx-dev-auth-key-and-cert.html) to generate the key pair:
  - `server.crt` - a public certificate that proves Discourse is the authorized app
  - `server.key` - a private key that signs Discourse’s APIs requests to Salesforce

2. Send the `server.crt` file to your Salesforce administrator so they can upload it in Step 3.
3. Hold onto the `server.key` to paste into the Discourse Salesforce settings in Step 5.

## Step 2: Create the External Client App in Salesforce

> **Role:** Salesforce administrator

1. Log into Salesforce.

2. Click the **gear icon** (⚙) in the top right and select **Setup**.

3. In the Quick Find box, search for **External Client App Manager** and select it.

4. Click **New External Client App**.

> **Note:** These steps use the **External Client App Manager** , introduced in Salesforce Spring '25. If your org is on an older release, the UI may say **App Manager** or **Connected Apps** instead — the underlying settings are the same.

## Step 3: Fill in Basic Information and OAuth Settings

> **Role** : Salesforce administrator

1. Fill in the **Basic Information** section (App Name and Contact Email are required).

2. Expand the **API (Enable OAuth Settings)** section and check the **Enable OAuth** setting.

3. Configure the following settings in this section:

4. Under **Certificate Upload** , click Upload files and upload the `server.crt` file from Step 1.

5. Click **Create**.

## Step 4: Retrieve the Consumer Key and Consumer Secret

> **Role:** Salesforce administrator

1. On the newly created External Client App, click the **Settings** tab.

2. Scroll down and expand the **OAuth Settings**.

3. Click **Consumer Key and Secret**.

4. Re-enter your Salesforce login credentials when prompted.

5. Copy the **Consumer Key** and **Consumer Secret** and send them to your Discourse admin for Step 5.

## Step 5: Configure the Discourse plugin settings

> **Role:** Discourse admin

1. In Discourse, go to **Admin** → **Plugins** → **Salesforce** → **Settings**.

2. Fill in the following settings:

3. Click **Save changes**.

## Step 6: Authorize the Discourse app in Salesforce

> **Role:** Salesforce integration user

1. Go to `https://<your-discourse-site>/salesforce/admin/authorize`, replacing `<your-discourse-site>` with your Discourse site’s full URL (e.g., `meta.discourse.org`).
2. You will be redirected to Salesforce and prompted to authorize the app.
3. Login to Salesforce and grant access to the app.

After completing this step, you should be all set. You can confirm it’s working by going to any user profile in Discourse — a **Sync with Salesforce** option should appear in the admin menu.

## Troubleshooting

If the plugin isn’t working after setup, check these first:

- **Admin dashboard health checks** : the plugin surfaces two alerts in `/admin` when things are misconfigured:

- **Enable verbose logging** : Turn on the `salesforce_auth_verbose_logging` site setting to write detailed authentication output to Discourse’s `/logs`. Common errors and causes:

| Symptom | Likely cause |
| --- | --- |
| “Insufficient privileges” when creating a Lead or Contact | The integration user doesn’t have Create/Edit permissions on Lead or Contact objects |
| “Insufficient privileges” when creating a Case | The integration user lacks Case or Case Comment permissions |
| “Invalid grant” on the authorization step | The RSA key doesn’t match the certificate uploaded in Step 3, or the JWT Bearer Flow wasn’t enabled |
| “DUPLICATE\_VALUE” error on Lead or Contact creation | Expected behavior if the user already exists in Salesforce — the plugin handles this, but see the main plugin docs for details |
| Chatter posts not appearing | The integration user may not have FeedItem Create permissions |

---

_[View the full topic](https://meta.discourse.org/t/how-to-configure-the-salesforce-integration/417136)._
