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

# CRM

The CRM area controls how Kernel connects to Salesforce, which objects it can read, where results are written, and what happened during each sync.

Start by deciding where Kernel data should go. Kernel recommends the Kernel Account custom object, `Kernel_Account__c`, so you can review Kernel data without replacing customer-owned fields on the Salesforce Account. A mapping can also write to Account or move data between two CRM objects when that is part of your setup.

{% hint style="info" %}
The [Kernel Account custom object](/integrations/salesforce-integration/custom-object.md) is the recommended destination for most setups. See the [object reference](/integrations/salesforce-integration/kernel-account-object-reference.md) for its standard fields.
{% endhint %}

## Connection

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

A Salesforce admin connects the org with an integration user. Salesforce permissions decide what Kernel can read and write.

The integration user normally needs:

* Read access to the source objects and fields that Kernel imports
* Read, Create, and Edit access to the destination object, such as `Kernel_Account__c`
* Read and Edit access to each destination field included in a sync mapping

Connection shows the active Salesforce environment and connection status. It also contains the nightly CRM import setting and the automatic refresh frequency for updated Kernel data.

{% hint style="info" %}
Before a larger sync, test one known account. Check that the value reaches the expected Salesforce object and field, then use the same mapping for the wider set.
{% endhint %}

For installation and permission details, see [Salesforce integration](/integrations/salesforce-integration.md).

## CRM objects

[Open CRM objects in Kernel](https://app.kernel.ai/crm/crm-objects)

CRM objects has two tabs:

* **Ingested objects** is where you bring in extra Salesforce data, such as Opportunity data.
* **New accounts** maps Kernel fields or fixed values to the Salesforce fields used when a workflow creates a record.

Use this page to confirm that Kernel can see the right object before you configure field mappings or run a sync.

## Configuration

[Open Configuration in Kernel](https://app.kernel.ai/crm-sync/configuration)

Configuration defines where Kernel writes data and which fields are enabled.

* **CRM push** maps Kernel fields to a Salesforce object, such as Kernel Account or Account.
* **In-CRM sync** maps data from one Salesforce object to another inside your CRM.

Open a mapping to choose the destination fields. If your team uses impact sets, you can also preview whether a sync would move accounts into or out of an important segment.

<figure><img src="/files/FTlN4AlLZIJYPMMaKVC5" alt="CRM Configuration page showing mappings from Kernel to the Kernel Account custom object and Salesforce Account"><figcaption><p>Each configuration names the destination object and shows how many fields are enabled.</p></figcaption></figure>

{% hint style="info" %}
Field mapping is directional. Check the source, destination object, and destination field before saving. A field with a similar name may still belong to a different Salesforce object.
{% endhint %}

## Syncs

[Open Syncs in Kernel](https://app.kernel.ai/crm-sync/syncs)

Syncs is the run history for CRM updates. Select a mapping to start a sync, then use the table to follow its progress.

Each run shows the destination object, number of accounts, successes, errors, and current status. Open **Monitor** for record-level details and generated files. This is the first place to check whether a run finished and whether every selected account reached Salesforce.

For scheduled and on-demand refresh behavior, see [Live scan enrichment](/integrations/salesforce-integration/enrich-with-kernel.md).