> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/app/data-setup.md).

# Data setup

Data setup prepares your CRM data for cleaning, hierarchy, and enrichment work. The setup path follows the same order as the app:

[Open Data setup in Kernel](https://app.kernel.ai/setup)

**Connect → Map fields → Risk scoring → Entity resolution**

Complete the steps in order. A later step relies on the connection and field choices made earlier.

{% hint style="info" %}
The exact setup path depends on your integration. Salesforce workspaces use all four steps. Other integrations, including S3, can follow a shorter path.
{% endhint %}

## 1. Connect

[Open Connection in Kernel](https://app.kernel.ai/settings/crm-connection)

Connect the Salesforce environment that Kernel should use. Confirm that the integration user can read the source account data and edit the Kernel destination fields.

The [Salesforce integration](/integrations/salesforce-integration.md) guide covers installation, authorization, and permissions. CRM destinations and sync history are covered on [CRM](/app/crm.md).

## 2. Map fields

[Open Field mapping in Kernel](https://app.kernel.ai/settings/field-mapping)

Field mapping tells Kernel where to find each input in your CRM. For example, map the Kernel **Account URL** input to the Salesforce Website field and **Parent Account ID** to the Salesforce Parent ID field.

The **Relevant for** labels show where each mapping is used, such as account identity resolution, cleaning actions, or risk tiering. Map the fields your team trusts. A reliable name, website, legal name, address, or parent can improve a difficult match. An unreliable field can make it worse.

<figure><img src="/files/Ic5fqa12SL6XIozXiDHG" alt="The Field mapping page matching Kernel inputs to Salesforce Account fields and showing what each mapping is used for."><figcaption><p>Each row maps one Kernel input to a CRM field. The labels on the right show which workflows use it.</p></figcaption></figure>

{% hint style="info" %}
Field mapping defines what Kernel reads. It does not choose where enrichment is written back. Configure write-back separately under [CRM configuration](https://app.kernel.ai/crm-sync/configuration).
{% endhint %}

## 3. Risk scoring

[Open Risk scoring in Kernel](https://app.kernel.ai/cleaning/risk-management)

Risk scoring controls how cautiously Kernel treats an account before recommending a cleaning action. You can set risk tiers, score CRM activity and related records, and add safeguards for accounts that should not be changed automatically.

Test the configuration on a sample before saving it for the full CRM. See [Risk management](/app/data-setup/configuration.md) for safeguards, scores, and tiers, and [Active users](/app/data-setup/active-users.md) for how account ownership affects risk.

## 4. Entity resolution

[Open Entity resolution in Kernel](https://app.kernel.ai/cleaning/master-data)

Entity resolution matches each CRM record to the real company behind it and assigns a [KERN ID](/concepts/kern-id.md). Review a sample before approval. Look at the matched entity, reasoning, confidence, and any fields that changed.

The identity mode tells Kernel which input to lean on when the record is ambiguous. URL bias leans on the website. Name bias leans on the account name. Other reliable evidence, such as a legal name, address, or contact domain, can still decide the match.

When the sample looks right, approve and lock the configuration. See [Entity resolution](/concepts/entity-resolution.md) for the full matching model.

{% hint style="info" %}
Approval locks the identity configuration used for future runs. Review the sample and selected identity mode before you approve it.
{% endhint %}

## Monitor inbound flows

[Open Inbound flows in Kernel](https://app.kernel.ai/cleaning/inbound-flow)

Inbound flows is a monitoring view today. It lists existing scheduled and API flows with their schedule, number of field mappings, status, and last update.

You cannot create a new inbound flow from this page yet. Use it to check whether an existing flow is active and when it last changed. Work with the Kernel team when a new flow or configuration change is needed.