Parent Category
A parent category is a data category that sits above one or more child categories inside a Salesforce data category group.
Definition
A parent category is a data category that sits above one or more child categories inside a Salesforce data category group. It is the higher node in a hierarchy, and the categories nested beneath it are its subcategories. Salesforce uses parent categories to organize Knowledge articles, and historically Ideas and Answers, into a browsable tree by topic.
Every data category group starts with a single top node named "All", which is the ultimate parent. Below "All" an admin builds out parent categories and their children, up to five levels deep. The structure controls both how content is grouped and who can see it.
How parent categories shape a data category hierarchy
Where parent categories live: the data category group
Parent categories do not exist on their own. They are nodes inside a data category group, which is the container an admin creates in Setup under Data Category Setup. When you make a new group, Salesforce gives it one fixed top node called "All". That "All" node is the root parent of everything you add later. From there you build the tree. Click a node and choose to add a subcategory beneath it, which makes the clicked node the parent. Or add a sibling at the same level, which gives the two nodes a shared parent. A category like "Products" can be a parent to "Hardware", "Software", and "Services", and each of those can in turn parent its own children. The default limits are generous. A single group can hold up to 100 categories across up to five hierarchy levels. Most orgs use far fewer. The hierarchy is logical, not physical, so moving a parent later carries its whole subtree with it. This is why a clean parent design at the start saves rework once thousands of articles are tagged.
Parent versus child, and what the labels really mean
The words parent, child, and subcategory describe position, not a special category type. The same category can be a child of the node above it and a parent of the nodes below it. "Hardware" is a child of "Products" and a parent of "Laptops" and "Monitors" at the same time. The only category that is purely a parent and never a child is "All", because nothing sits above it. This matters when you read Salesforce documentation or talk to a consultant. A reference to the parent category usually means the node directly above the one you are looking at. A reference to subcategories means everything nested under a given parent. Articles attach to categories at any level, so an author can tag a record on a broad parent like "Products" or a narrow child like "Laptops". Picking the right level affects how easily users find the content later. Tag too broadly and the parent fills with unrelated articles. Tag too narrowly and casual browsers may miss it. Good taxonomies use parents for browsing and children for precision.
Visibility flows up and down the tree
Parent categories are central to how Salesforce controls article access. Data category visibility is set per role, permission set, or profile, with three options: All categories, None, or Custom. Custom is where the hierarchy becomes powerful. When you grant a user a single category, Salesforce implicitly includes both that category's parents and its children. Take a geography group. If a user is granted the "America" category, they automatically see its parent "All Countries" and its child "USA". Visibility climbs to every ancestor and descends to every descendant of the granted node. This rule means you rarely grant every category by hand. You grant the level that fits a person's scope and let inheritance do the rest. A regional support agent might be granted their region's parent category, which opens that whole branch while keeping other regions closed. Because the inheritance is automatic, a poorly placed category can leak more than you intend. Always check the parent chain of any category before you grant it, since granting a deep child still reveals everything above it.
Querying across a parent and its children in SOQL
Developers reach data categories through the WITH DATA CATEGORY clause in SOQL, used against objects like KnowledgeArticleVersion and Question. The clause filters records by their category, and it understands the parent-child tree through filter selectors. There are four selectors. "At" matches the exact category only. "Above" matches the category and its ancestors. "Below" matches the category and its descendants. "AboveOrBelow" matches the whole branch, the category plus everything above and below it. A query like WITH DATA CATEGORY Geography__c BELOW America__c returns articles tagged on "America" and on every child such as "USA". This is how a self-service portal shows all articles under a chosen parent without listing each child by name. The selector you pick mirrors the intent a parent category encodes in the UI. Choose "Below" when a user clicks a parent and expects to see everything inside it. Choose "At" when you want only the records pinned to that exact node. Understanding the selectors prevents the common bug of returning too many or too few articles from a category branch.
Where you meet parent categories beyond Knowledge
Knowledge is the most common home for parent categories, but the data category framework was shared across several features. Ideas and the older Answers and Chatter Answers communities also used data category groups to sort posts by topic, so a parent category there grouped ideas the same way it groups articles. This shared design is why the term shows up in different corners of the product. An Ideas zone could be tied to a category group whose parent categories let members filter ideas by product line. Salesforce has since steered customers toward newer tools, so most active hierarchies you see today sit behind Lightning Knowledge. The concept still translates cleanly. Whatever the front end, a parent category is the broader bucket and its subcategories are the narrower ones. Keep in mind that data categories are different from a record type or a topic. Record types control page layouts and picklist values. Topics are free-form crowd tags. A parent category is a fixed, admin-governed node in a controlled tree that drives both organization and access at once.
Designing a parent hierarchy that lasts
A parent category structure is hard to redesign once it carries live content and visibility rules, so plan it before you scale. Start from how people actually look for answers, not from your internal org chart. If customers think in product lines, make product lines your top parents. If agents think by region, lead with geography. The top parents are the first thing a browsing user sees, so they should read as obvious buckets. Keep the tree shallow where you can. Five levels are allowed, but deep trees are tiring to browse and easy to mis-tag. Two or three levels under "All" handle most needs. Name parents broadly and children specifically, and avoid putting the same concept under two different parents, which confuses both authors and the visibility model. Revisit the hierarchy as the article library grows, since a parent that once held a dozen articles may need to split into several when it holds hundreds. Because visibility inherits through parents, document which roles map to which branch so future admins do not accidentally widen access by granting the wrong node.
How to build a parent category hierarchy
You create parent categories by building out a data category group in Setup. The group gives you the fixed "All" root, and from there you add parents and nest children beneath them.
- Open Data Category Setup
From Setup, type Data Category in the Quick Find box and select Data Category Setup. You see any existing category groups. Create a new group or click into an existing one to edit its tree.
- Add a top-level parent under "All"
Select the "All" node, then add a category. Categories you add directly under "All" become your top-level parents, such as Products or Geography. Give each a clear, broad name that users will recognize when browsing.
- Nest child categories
Click a parent node, then add a subcategory to place a child beneath it. Repeat to build the branch. To add a peer at the same level, add a sibling instead, which shares the same parent. Stay within five levels deep.
- Activate the group
Activate the category group so authors and users can use it. An inactive group is invisible to everyone except setup. Activation is what makes the parent hierarchy available on article edit pages and in search filters.
- Set category visibility
Configure visibility per role, permission set, or profile. Choose All, None, or Custom, and grant the parent level that fits each audience. Remember that granting a category also reveals its parents and children automatically.
The fixed top parent every group starts with. You cannot remove it; all your parent categories hang beneath it.
Places a new category as a child of the selected node, making the selected node its parent in the tree.
Places a new category at the same level as the selected node, so both share the same parent.
The role, permission set, or profile setting (All, None, or Custom) that decides which categories, and therefore which branches, a user can see.
- Granting a deep child category still reveals every parent above it, so a "narrow" grant can expose a whole branch.
- The default ceiling is 100 categories per group and five hierarchy levels; plan the parent tree to live within them.
- An inactive category group is hidden from authors and users, so a freshly built hierarchy does nothing until you activate it.
- Moving a parent later relocates its entire subtree, which can shift the visibility and tagging of many articles at once.
Trust & references
Cross-checked against the following references.
- Create Data Categories for Articles, Answers, and IdeasSalesforce
- Data Category VisibilitySalesforce
Straight from the source - Salesforce's reference material on Parent Category.
- Work with Data CategoriesSalesforce
- WITH DATA CATEGORY (SOQL and SOSL Reference)Salesforce
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 runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Parent Category?
Q2. What can categories control besides organization?
Q3. Where are data categories used?
Discussion
Loading discussion…