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

# Accounts

Browse imported accounts, inspect identity and hierarchy data, and export the view you need.

Accounts is where you inspect the records Kernel has imported from your connected sources or CSV files. Use [Explore](https://app.kernel.ai/accounts) to find an account, review what Kernel matched it to, and choose which CRM and Kernel fields you want to see.

## Explore accounts

The toolbar above the table contains the main controls:

* **Search** finds accounts by name or URL.
* **Filter** narrows the list by field values. Salesforce workspaces can use field rules or SOQL, and can include records that have been deleted from the CRM.
* **View settings** lets you choose which Kernel and CRM fields appear as columns.
* **Export CSV** downloads the accounts in your current scope.

Each row starts with the account name and website. The remaining columns come from your current view settings. Select a row to open its details.

{% hint style="info" %}
Start with a small set of fields that answer the question you are working on. You can add more CRM or Kernel columns at any time.
{% endhint %}

## Understand the identity

The table brings together a CRM record and Kernel's resolved identity. These terms describe different things:

| Term               | What it means                                                                                                                                                                      |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **CRM record**     | The account row stored in your CRM, with its own CRM ID and fields.                                                                                                                |
| **Matched entity** | The real organization Kernel determined that the CRM record represents. Learn more about [entities](/data/entity-data.md) and [entity resolution](/concepts/entity-resolution.md). |
| **KERN ID**        | Kernel's persistent identifier for that matched entity at that exact level. Read [What is a KERN ID?](/concepts/kern-id.md).                                                       |

{% hint style="info" %}
A KERN ID belongs to the matched entity, not the CRM record. Two CRM records that resolve to the same organization can share a KERN ID. A parent and subsidiary have different KERN IDs because they are different entities.
{% endhint %}

If you use the Kernel Account custom object in Salesforce, **Linked Account** connects that Kernel Account record to its Salesforce Account. It is a Salesforce relationship field. KERN ID identifies the company Kernel resolved the account to.

### A domain is one input, not the whole match

Kernel does not rely on the website alone. When the data is available, entity resolution can also use the account name, legal name, country, address, LinkedIn URL, related and contact domains, parent relationships, and opportunity context.

Map the relevant source fields in [Connections > Salesforce > Data flows](/platform/data-setup.md) so Kernel has the context it needs. The [entity resolution guide](/concepts/entity-resolution.md) explains how those signals are combined.

### Top operating parent is not the full hierarchy

The **top operating parent** is the highest active operating company in an ownership chain. It is often the most useful anchor for territories, account planning, and go-to-market work.

It is still one point in the hierarchy. Use the hierarchy fields when you need the immediate parent, legal top parent, top operating parent, or the full chain between them. Read [Hierarchies](/data/hierarchies.md), [Parent relationships](/data/hierarchies/parent-relationships.md), and the [Data dictionary](/data/data-dictionary.md) for field definitions.

{% hint style="info" %}
Use top operating parent for a practical operating group. Use the full hierarchy when legal ownership or every level in the chain matters.
{% endhint %}

## Open account details

Select an account row to open the detail drawer. It puts the main review information in one place:

* KERN ID and CRM ID
* identity confidence
* risk tier and recommended cleaning action
* a comparison of the original CRM values and Kernel's resolved values
* the CRM sync difference, when sync is configured
* all available fields and data freshness information

Controls such as **Change identity**, **Reject identity**, and **Sync to CRM** only appear when they are enabled for your workspace.

## Import accounts

Select **Import accounts** on the Accounts page. Choose a source, select the accounts to include, then review the import.

### Salesforce

Choose one of three ways to select accounts:

* **Whole org** includes all Account records in the connected Salesforce org.
* **Filter builder** lets you choose fields, comparisons, and values. Accounts must match every filter.
* **Query** accepts a SOQL WHERE clause. Add `LIMIT` to try a smaller sample, up to 10,000 records.

Field mappings come from [Connections > Salesforce > Data flows](/platform/data-setup.md).

### CSV upload

Choose a CSV and check the suggested column mappings. Map **External ID**, **Company name**, and at least one of **Website** or **LinkedIn URL**. You can also map Legal name, Street, City, State, and Country.

Use a stable external ID for each account so Kernel can recognise records already imported. Choose **None** for columns you do not want to map.

### Amazon S3

Select **Amazon S3** to import new rows from the file configured in your S3 connection. The dialog shows the file path, detected rows, and when the file last changed. See [S3 file exchange](/integrations/s3-integration.md) to set up the file and its mappings.

### Review and import

The final step shows how many records are new to Kernel and how the import affects your tracked-account usage. Existing records are skipped. Select **Import** to start; accounts appear in the table as they finish processing.