Hierarchies

How Kernel links entities into corporate trees

Hierarchy data explains how one resolved entity relates to another. Kernel keeps each entity distinct, assigns each one its own KERN ID, and links related entities into a tree.

This matters because a CRM account can mean different things. It might be the global group, a country subsidiary, a holding company, a product brand, or a standalone business. Kernel keeps those boundaries visible instead of folding every related record into one company.

What hierarchy data answers

Use hierarchy data when you need to know:

Question	Use
Who is directly above this account?	CRM parent fields, association actions, and account ownership cleanup
What is the top of the corporate tree?	Routing, reporting, account-family lists, and rollups
Is this the highest operating company below a holding company?	GTM views that should skip passive holding companies
Is this account a regional subsidiary?	Territory planning, regional reporting, and duplicate policy
Which scope should a number use?	Entity-level vs. consolidated headcount and revenue

Pages in this section

• Parent relationships explains immediate parent, top parent, top operating parent, and standalone companies.

• Regional subsidiaries explains how Kernel distinguishes a regional subsidiary from a duplicate account.