> ## 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 Overview

> What the Salesforce Data Cloud connector covers, what Prizm collects, and how it authenticates.

Prizm connects to Salesforce Data Cloud (also called Data 360) to catalog your Data Lake Objects and Data Model Objects, monitor volume and schema changes, run data quality checks, and trace lineage from the data source through to downstream assets. The connector is read-only.

## Why Connect Salesforce Data Cloud to Prizm?

**Catalog & Context** Prizm discovers Data Lake Objects (DLOs) and Data Model Objects (DMOs), including each object's fields, category, and relationships, and adds them to the Prizm catalog. Data Spaces map to domains.

**Data Quality** Quality rules run against your Data Cloud objects using the Data Cloud query API. Key qualifier fields automatically get uniqueness rules, and referential-integrity rules are suggested from DMO relationships. You can edit or disable any automatic rule.

**Observability** Prizm tracks row counts and detects added, dropped, and type-changed fields between catalog runs.

**Lineage** Prizm builds native lineage from the Data Cloud metadata: Data Source Object to DLO to DMO to Calculated Insight to Segment to Activation, plus Data Transform sources to targets.

**Criticality** Each object receives a criticality score from its dependencies, volume, metadata, key attributes, and structure.

## Authentication

The connector uses the OAuth 2.0 **Client Credentials** flow with a Salesforce Connected App or External Client App. Username and password authentication isn't supported. You provide your org's My Domain URL, the app's Client ID (Consumer Key), and its Client Secret, or retrieve them from a vault. See [Setup](/sources/salesforce-data-cloud/setup).

## Current Scope

The connector is read-only. Prizm never writes back to Salesforce, and quality exceptions are stored in an Iceberg table.

The following aren't covered or aren't available yet:

* Reports and Dashboards, which are planned but not yet available.
* Usage analytics such as query history. Data Cloud doesn't expose a public API for it.
* Freshness, unless a refresh timestamp can be retrieved through the API. Otherwise it shows as Unknown.
* Data Shares and Data Graphs, CRM Analytics pipelines, model execution or retraining, and write-back.

## Next Steps

> **[Setup](/sources/salesforce-data-cloud/setup)**
>
> Create the Salesforce app and connect Data Cloud to Prizm.

> **[What We Collect](/sources/salesforce-data-cloud/what-we-collect)**
>
> The metadata, signals, and lineage Prizm extracts.

> **[FAQ](/sources/salesforce-data-cloud/faq)**
>
> Common questions about the Salesforce Data Cloud connector.

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


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