Category Group for Articles
Category Group for Articles is the Salesforce Knowledge taxonomy structure that organises articles into hierarchical Data Categories along a named dimension (Product, Topic, Geography, Audience).
Definition
Category Group for Articles is the Salesforce Knowledge taxonomy structure that organises articles into hierarchical Data Categories along a named dimension (Product, Topic, Geography, Audience). Each Category Group represents one dimension, containing nested Data Categories that articles get tagged with. A typical Knowledge implementation runs two or three Category Groups in parallel: a Product hierarchy for what the article is about, a Region hierarchy for where it applies, and sometimes a Lifecycle hierarchy for content maturity. Articles can tag against one or many categories per group; readers narrow by category to find relevant content.
Category Group for Articles is configured in Setup, Data Category Setup. Admins build the tree, assign per-profile visibility, and link the Category Group to the Knowledge object so authors can categorise articles. The model is the same Data Category infrastructure that powered the retired Answers feature; for Knowledge, the term and the feature both survive. Visibility per profile lets admins expose different slices of the taxonomy to different audiences. Reporting filters by Data Category to slice content metrics by Product, Region, or any other dimension the org models. The Category Group is the foundation of any Knowledge program; misdesign here propagates to every downstream report and search experience.
How Category Groups for Articles shape Knowledge programs
Category Group structure
Each Category Group has a Name, a Label, and a tree of Data Categories. The tree can be nested several levels deep. Authors tag articles against one or more categories per group; visibility per profile decides who sees which slice. Setup, Data Category Setup is where it all happens.
Common Category Groups in practice
Production Knowledge programs typically run Product, Region, Audience, and Article Type as separate Category Groups. The first names what the article is about; the second names where it applies; the third names who it is for; the fourth names what kind of content it is. Adding more dimensions seems flexible but quickly becomes unmanageable; cap at three or four.
Data Category Visibility
Visibility per profile decides which Data Categories each user role can see. A B2B partner profile may see only partner-relevant branches; an internal Support profile sees everything. Visibility cascades down the tree by default. Most production setups configure visibility explicitly per Category Group rather than relying on cascade alone.
Tagging articles
Authors tag articles against Data Categories during authoring or editing. The Knowledge Article Categorisation panel exposes the Category Groups configured for Knowledge. Tagging is multi-select per group, so an article can carry both Region: North America and Region: EMEA.
Reporting on Data Category dimensions
Reports filter Knowledge articles by Data Category. Common reports: article count per Product, average article age per Region, archive rate per Audience. The Category Group dimension is what makes the reporting useful; without categorisation, Knowledge reports collapse to a single bucket.
Experience Cloud and category browsing
Help Center and Customer Service Experience Cloud templates expose Data Categories as browse trees. Customers narrow by category to find related articles. The same Category Group structure powers both internal Knowledge sidebar search and external Help Center browse.
Migrating category structure over time
Reshaping a Category Group (renaming categories, adding levels, splitting branches) is supported but disruptive. Existing tagged articles need re-tagging when categories merge or split. Plan structural changes with a clear migration plan; admins routinely under-estimate the cleanup effort.
Common design pitfalls
Three patterns recur. Too many Category Groups (five-plus) overwhelm authors and make tagging inconsistent. Too few collapse useful dimensions. Visibility misconfiguration exposes confidential content to the wrong profiles. Each is addressable with deliberate up-front design.
How to design Category Groups for Articles
Category Group design is foundational. Get it right at launch; reshaping after thousands of articles tag against the structure is painful.
- Identify the dimensions you need
Most programs need Product, Region, Audience. Some add Lifecycle, Channel, or Compliance. Cap at three or four; more becomes unmanageable.
- Build each Category Group
Setup, Data Category Setup. Create the Category Group, name the categories, build the tree to the depth needed. Three levels usually suffices; deeper is rarely worth the navigation cost.
- Configure per-profile visibility
For each Category Group, set visibility per profile. Most production setups explicitly configure visibility rather than relying on cascade defaults.
- Link to Knowledge
Ensure the Category Group is associated with the Knowledge object so authors can tag articles.
- Train authors on tagging conventions
Document how to tag articles per Category Group. Inconsistent tagging is the single biggest reason Knowledge reports stop being useful at scale.
- Too many Category Groups overwhelm authors. Cap at three or four.
- Reshaping categories after thousands of articles tag against them is painful. Design carefully up front.
- Visibility misconfiguration exposes confidential content. Audit visibility per Category Group regularly.
- Deeper than three levels rarely justifies the navigation cost. Keep trees shallow.
Trust & references
Cross-checked against the following references.
- Data Category GroupsSalesforce Help
- Knowledge OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Category Group for Articles.
- Data Category VisibilitySalesforce Help
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 does a Category Group for Articles do?
Q2. Can multiple Category Groups apply to the same article?
Q3. What other purpose do Category Groups serve besides browsing?
Discussion
Loading discussion…