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

# Risk management

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

Risk management tells Kernel how cautious to be with each account. It combines safeguards, a risk score, and account ownership signals to decide which changes can run in bulk and which ones need review.

{% embed url="<https://pub-8e1d08f439ec43bdbb79f1055a273a02.r2.dev/configure-risk-change-management-04926186.mp4>" %}

## Risk scores and tiers

Every account receives a score from 0 to 100 and a corresponding risk tier. A higher score means the account needs more care before it is changed.

<figure><img src="/files/UrRVSZgqzmzgl01Z2FCB" alt="Four Kernel risk tiers, from very low risk to high risk"><figcaption><p>Risk tiers turn the underlying score into a practical review threshold.</p></figcaption></figure>

The default tiers are:

* **Very low risk:** safe to include in bulk actions
* **Low risk:** likely safe to include in bulk actions
* **Medium risk:** review case by case
* **High risk:** review or exclude

Your Kernel team can adjust the score thresholds for your workspace.

## Safeguards

Safeguards take priority over the risk score. If an account matches a safeguard, Kernel gives it a score of 100 and protects it from destructive actions.

Common safeguards include:

* accounts with open opportunities
* accounts where `Type` is Customer
* accounts with associated ARR

You can build safeguards with standard or custom fields on the Account object.

## Risk scoring

For accounts that do not match a safeguard, Kernel calculates a score from CRM activity and context. The standard inputs include:

* recent activity, using `LastActivityDate`
* record age, using `CreatedDate`
* open and closed opportunities
* tasks from the last three years
* associated contacts
* owner type
* completion of important CRM fields

Each input has a weight from Very low to Very high. You can change those weights or add fields that matter to your team.

Higher-scoring records are also more likely to remain as the primary account when duplicates are merged.

### Custom fields

Any CRM field can contribute to the score. Choose the field, set the conditions that matter, and give it a weight that reflects its importance.

<figure><img src="/files/z2VftX0Bl0TaAjjqHGFn" alt="Custom CRM fields added to Kernel risk scoring"><figcaption><p>Custom fields let the risk model reflect the way your team manages accounts.</p></figcaption></figure>

## Account ownership

Account ownership is part of the risk model. An account may be a duplicate or belong to a closed business, but changing it can still disrupt a rep who is actively working it.

Use [Active users](/app/data-setup/active-users.md) to define active, inactive, and integration users. Kernel uses those definitions when it evaluates account ownership.

## How risk management is used

Start bulk cleaning with very low and low-risk accounts. Review higher-risk accounts separately or exclude them from the action. This lets most of the CRM move forward while sensitive records get more attention.

See [Data actions](/app/actioning.md) for how to review and run account changes with these controls.