> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce Data Cloud Setup

> Prerequisites, OAuth scopes, and step-by-step instructions for connecting Salesforce Data Cloud to Prizm.

## Prerequisites

| Requirement | Notes |
| :- | :- |
| Salesforce org with Data Cloud | Your Data Cloud license, or a connected companion org |
| A Connected App or External Client App | Salesforce recommends External Client Apps. New Connected App creation is restricted as of Spring '26, but existing Connected Apps keep working |
| OAuth scopes | `cdp_query_api`, `cdp_profile_api`, `api`, and `refresh_token` (see below) |
| My Domain URL | For example `yourorg.my.salesforce.com` |
| Prizm platform storage | Needed for quality exceptions |

### Required OAuth Scopes

| Scope | Purpose |
| :- | :- |
| `cdp_query_api` | Run ANSI SQL queries. Required for profiling and quality scans |
| `cdp_profile_api` | Read profile and entity data |
| `api` | Core API access, token exchange, and the Metadata API |
| `refresh_token` | Unattended, scheduled access |

> [!NOTE]
>
> When you validate the connection, Prizm checks the token exchange and the granted scopes. A missing scope is reported by name, for example `Missing: cdp_query_api`.

## Create the Salesforce App

In Salesforce Setup, create an External Client App (or use an existing Connected App) and configure it for the Client Credentials flow. The exact menu names vary by Salesforce release, so follow Salesforce's documentation for your org. In outline:

**1. Create the app**

Create an External Client App, and enable OAuth settings for it.

**2. Add the scopes**

Add the four scopes listed above.

**3. Enable the Client Credentials flow**

Enable the Client Credentials flow, and choose the user the app runs as. This user needs access to the Data Cloud objects you want Prizm to read.

**4. Copy the credentials**

Copy the app's Consumer Key (Client ID) and Consumer Secret (Client Secret). Salesforce shows the secret only through the app's consumer details, so store it safely.

## Connector Setup

**1. Open the connector wizard**

Navigate to **Source** and click the **+** icon next to the source list. Search for **Salesforce Data Cloud** and select it from the connector grid.

**2. Enter source details**

| Field | Description |
| :- | :- |
| Connection Name | A label for this connection (for example, `sfdc-data-cloud-prod`) |
| Description | Optional notes about what this connection covers |
| Authentication Type | **Client Credentials** |
| My Domain URL | Your Salesforce My Domain URL (for example, `https://your-org.my.salesforce.com`) |

![The Salesforce Data Cloud Source Details form](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/sources/salesforce-data-cloud/form.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=115bcbde6b31b295397184506e8d3b15)

**3. Provide credentials**

Toggle **Use Vault** to retrieve the credentials from a vault instead of entering them.

**Client ID & Client Secret (default)**

| Field | Description |
| :- | :- |
| Client ID | The app's Consumer Key |
| Client Secret | The app's Consumer Secret, stored encrypted |

**Use Vault**

Choose a vault already configured for your organization and give the key where the Client ID and Client Secret are stored.

**4. Validate and choose scope**

Click **Next** to validate the connection, then use the Data Space include and exclude options to choose which Data Spaces Prizm should catalog.

**5. Save**

Complete the configuration. The source then appears in the **Source** list, where the **Valid** column shows a green check for a working connection. Assets appear in the catalog once the first scan completes.

## Next Steps

> **[What We Collect](/sources/salesforce-data-cloud/what-we-collect)**
>
> See what Prizm extracts from Data Cloud.

> **[FAQ](/sources/salesforce-data-cloud/faq)**
>
> Common questions about authentication, scopes, and scoping.

> **[Troubleshooting](/help/troubleshooting)**
>
> Diagnose connection failures, permission errors, and timeouts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.