Parent Category
A parent category is a data category that sits directly above one or more child categories inside a Salesforce data category group.
Definition
A parent category is a data category that sits directly above one or more child categories inside a Salesforce data category group. The label describes position in a hierarchy, not a separate kind of record, so any category with something nested beneath it is a parent.
Salesforce supports up to 5 levels in a data category group hierarchy, which leaves room for a node to be a parent several steps below the top.
The tree does two jobs at once. It gives users a browsable structure for Knowledge articles, and it filters what each of them can read, because visibility is granted on categories rather than on individual articles.
In plain English
“Think of a filing cabinet drawer labeled Products. Inside it are folders for Laptops and Phones. The drawer is the parent, the folders are its children. Open the drawer and you get everything inside it, which is close to how Salesforce decides what people are allowed to read.”
Worked example
A support team at a solar equipment company builds a data category group called Product Lines. Under the root node, renamed All Product Lines, they add three parent categories: Solar Panels, Inverters, and Batteries. Solar Panels gets two children, Residential Panels and Commercial Panels. An article on panel mounting is tagged to Residential Panels. A permission set grants field technicians visibility on Solar Panels only. Those technicians still see the mounting article, because visibility runs down from the granted parent to its children, and they see All Product Lines above it. Inverters and Batteries stay hidden, because sibling branches are excluded.
How the parent and child relationship actually behaves
The All node that every group starts with
You do not create a parent category on its own. You create a data category group in Setup (Quick Find, then Data Category Setup), and the new group ships with a single root node labeled All. Most admins rename it right away, which is why Salesforce's own documentation shows All Sales Regions and All Products at the top of its examples. Click a node and add a subcategory beneath it, and the node you clicked becomes a parent. Add a sibling instead and both nodes share whatever sits above them.
Parent and child are positions, not types
Hardware sits under Products and above Laptops and Monitors, which makes it a child and a parent at the same moment. Nesting something beneath a node does not change the node itself. It picks up a second role and keeps the first one. That matters when you tag articles, since authors can attach a record at any level. A broad parent collects everything and gets noisy. A narrow child is precise but easy for a browsing user to miss.
Visibility travels up and down the branch, never sideways
Category visibility is granted per profile, permission set, or role, and the setting never stays confined to the node you pick. Grant one category and Salesforce includes its ancestors and its descendants. Grant America and the user also gets All Countries above it and USA below it. Sibling branches stay closed, which is how most orgs keep regions or product lines apart. The trap is assuming a deep grant is a narrow grant. Everything above the node you chose opens too, so read the full parent chain before you save.
Filter selectors mirror the hierarchy in SOQL
Developers reach the same tree through the WITH DATA CATEGORY clause on objects like KnowledgeArticleVersion and Question. Four selectors describe the relationship you want. AT selects the specified category. ABOVE selects it and all its parent categories. BELOW selects it and all its subcategories. ABOVE_OR_BELOW selects the category, its parents, and its subcategories. So WITH DATA CATEGORY Geography__c BELOW northAmerica__c returns articles tagged on that parent and on usa__c beneath it. Only AND is supported when you combine category filters, so OR will not compile.
Limits, and why rearranging a parent is expensive
A single group holds up to 100 categories across a maximum of five levels, which is more room than most taxonomies need. Two or three levels under the root are easier to browse and less likely to be mis-tagged. Plan the top parents around how people search, by product line or region, because those buckets are the first thing anyone sees. Deploying a group through the Metadata API is unforgiving: any category missing from your XML is permanently removed, along with the record categorizations that used it.
How organizations use Parent Category
Groups its knowledge base under one parent category per product line, then grants each regional service team the single branch it supports.
Puts Programs at the top of the tree with each grant program as a child, so a volunteer coordinator sees only their own articles.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Parent Category.
Hands-on resources to go deeper on Parent Category.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
+5 pts / dayQ1. In a WITH DATA CATEGORY clause, what does the BELOW filter selector return?
Q2. A user is granted visibility on a child category three levels down. What else becomes visible to them?
Q3. What does Salesforce do when you create a new data category group?
Discussion
Loading discussion…