Active users

Define who owns your accounts and how Kernel categorizes those users

Kernel uses the account owner's category in risk scoring and data action rules. This helps distinguish accounts managed by people from accounts owned by integrations or inactive users.

Open Connections > Salesforce > Configure risk > User type definition.

Open User type definition in Kernel

Category	Meaning
Active	A person who meets your active-user rules or Kernel's default active-user checks.
Inactive	A person you have marked inactive, or who meets the inactive-user checks.
Integration	A user used by software or an automated process.
Unknown	The owner is missing, cannot be found, or does not match a rule when default categorization is off.

Choose the owner field

Kernel uses the Salesforce account owner field, OwnerId, by default.

If your team tracks ownership in another account field, select it in Custom owner field. Choose a field that identifies a Salesforce user, such as a user lookup for your account manager.

Assign specific users

Use Active user and Inactive user to assign named users directly. These assignments take priority over conditions and default categorization.

For example, add a shared holding user to Inactive user, or add an account executive to Active user. If the same user is in both lists, the inactive assignment takes priority.

Add conditions

Add conditions under Active user conditions, Inactive user conditions, or Integration user conditions. Choose a user field, its type, an operator, and a value.

Use conditions for groups of users. For example, classify a user as Integration when a custom System User checkbox equals true, or classify a user as Inactive when their department equals RevOps.

Every condition within a category must match. An empty category has no effect. If a user matches conditions in more than one category, Kernel checks Active first, then Inactive, then Integration.

Add conditions to identify active and inactive users.

Default categorization

Keep Fallback to Kernel's default categorization on to classify users who do not match your assignments or conditions. It is on by default. Turn it off to leave those users as Unknown.

Kernel's default checks run in this order:

1. Integration: the user's name or username contains an integration term; their profile is API-only; or their Salesforce User Type is Integration or Api Only User.

2. Inactive: the Salesforce user is inactive, their last login was more than 90 days ago, or their profile is System Administrator.

3. Active: none of the integration or inactive checks match.

The integration terms are integration, salesforce, service account, zoominfo, ringlead, automated, webhook, webhooks, marketo, and sync. Matching ignores capitalization. For an email address, Kernel checks the part before @.

A missing last login date does not, on its own, make a user inactive. A RevOps job title does not, on its own, make a user inactive either. Use a direct assignment or condition if your team wants those users classified differently.

Which rule wins?

Kernel stops at the first match:

Priority	Check
1	User is in the Inactive user list.
2	User is in the Active user list.
3	All Active user conditions match.
4	All Inactive user conditions match.
5	All Integration user conditions match.
6	Default categorization, if enabled.

If the owner is missing or cannot be found, the result is Unknown unless a direct user assignment already applies.

Click Save at the bottom of Configure risk to save the owner field, user assignments, and conditions along with your other risk settings.