Data Categories
Data Categories in Salesforce are admin-defined hierarchical classifications used to organize Knowledge articles and Answers questions for filtered access, search scoping, and visibility control.
Definition
Data Categories in Salesforce are admin-defined hierarchical classifications used to organize Knowledge articles and Answers questions for filtered access, search scoping, and visibility control. Each Data Category Group (Geography, Product Line, Issue Type, Audience) contains a tree of Data Categories (North America > United States > California; Cloud Products > Sales Cloud > Pipeline Management). Articles and questions are tagged with one or more categories from each group; users browse, filter, or search within categories that match their context.
Data Categories exist because Knowledge bases grow to thousands of articles, and a flat list becomes unusable. The category hierarchy lets admins control which articles surface for which users (Geography categories let a US user see US-specific articles), which articles appear together (Product Line categories let related articles cluster in search results), and which articles a Knowledge user can access (Category Group Visibility settings gate access per profile). Categories are how Knowledge scales from dozens of articles to tens of thousands.
Why Data Categories are the foundation of any Knowledge base past a few dozen articles
Where Data Categories live in setup
Setup, Data Category Setup. The page lists every Data Category Group (Geography, Product, Issue Type) with the hierarchy under each. New Category Group creates a new top-level grouping; within a group, admins build the tree of categories with drag-and-drop. Each category can have child categories up to five levels deep. Categories are global within a group; an article tagged Geography > North America > United States > California holds all four levels of the hierarchy implicitly.
Category Group Visibility and the access control layer
Setup, Data Category Visibility (or Data Category Group Visibility per profile) controls which categories each profile can see. A US support agent's profile might be configured for Geography > North America > United States (and all children); a global compliance reviewer's profile is configured for All Categories. Articles tagged with categories the user cannot see do not appear in search or browse results. The visibility setting is the most consequential Knowledge access control; misconfiguration hides articles users need or exposes articles they should not see.
Tagging articles with categories
Knowledge article authors tag each article with categories from each relevant group. An article about US California tax requirements might be tagged Geography > North America > United States > California plus Product > Billing Module plus Issue Type > Tax. The tagging surface appears on the article edit page; categories from each group can be picked, multiple per group are allowed (an article applies to both US and Canada), categories implicitly inherit (tagging California also tags United States and North America). The tagging is the article's metadata; without it, the article exists but does not surface in filtered search.
Data Categories in Knowledge search and the user experience
Knowledge search uses Data Categories for filtered queries. A support agent searching for password reset can filter the search to Product > Account Management > Authentication, getting only articles tagged with that branch. The Lightning Knowledge component supports per-search category filters. Salesforce search also weights category proximity in ranking; an article tagged exactly with the user's context ranks higher than an article tagged at a higher level only. The search experience is meaningfully better with categories than without.
Categories and channel-specific Knowledge
Knowledge articles are also tagged with Channels (Internal App, Customer, Partner, Public Knowledge Base). Channels work alongside Data Categories. A category-scoped customer-channel search shows public articles in the customer's product category; the same search by an internal agent shows internal-only articles too. The combination of Channel and Category is the access matrix; both need correct tagging for Knowledge to deliver the right article to the right user.
Recategorization, retirement, and lifecycle
Category groups and individual categories can be added, renamed, or deleted. Deletion is more impactful; articles tagged with a deleted category lose the tag. Most orgs structure their categories deliberately at Knowledge rollout and rarely add new ones. The hierarchy reflects the business taxonomy (product lines, geographies, issue types); changes to the taxonomy ripple through the article tagging. Major restructures are operationally heavy; plan deliberately and execute in a sandbox first.
Limits and scaling considerations
Each org supports up to 5 active Data Category Groups, up to 100 categories per group, and up to 5 levels of nesting. The limits are generous for most organizations but tight for highly diverse global operations. Workarounds include using fewer groups with deeper trees, combining related dimensions into one group, or building secondary categorization via custom fields on Knowledge that the Knowledge search can also filter on. The limits drive design; understanding them at rollout prevents painful restructures later.
How to set up Data Categories for a scalable Knowledge base
The setup is one-time but consequential. Design the taxonomy carefully with Knowledge owners, configure visibility per profile, train article authors on tagging, audit periodically. Skipping the taxonomy design produces categories that do not match how users actually search; the cleanup is painful.
- Design the category taxonomy with Knowledge owners
Workshop with the Knowledge team. What dimensions matter for filtering: geography, product, issue type, audience. Each dimension becomes a Category Group.
- Enable Data Categories in Setup
Setup, Data Category Setup, Enable. The feature is available with Knowledge editions.
- Create the Category Groups
Up to 5 active groups. Name per the dimension (Geography, Product Line, Issue Type, Audience). Document the rationale.
- Build the category trees
Within each group, build the hierarchy. Up to 100 categories per group, up to 5 levels deep. Match the structure to how users mentally categorize.
- Configure Category Group Visibility per profile
Setup, Data Category Visibility. For each profile, pick which categories from each group the profile can see. The configuration is the access control layer.
- Train article authors on tagging
Authors who do not understand the categories tag inconsistently. A 30-minute training covers the taxonomy, the tagging UI, the rationale.
- Audit article-to-category coverage quarterly
Pull articles without category tags or with sparse tagging. The audit catches gaps before they affect search quality.
Top-level dimensions. Up to 5 active per org.
Up to 5 levels of nesting per group. Deeper trees more specific but harder to maintain.
Per-profile setting controlling which categories the user can see.
Internal App, Customer, Partner, Public KB. Works alongside Data Categories for access.
Allowed; an article can apply to multiple geographies or product lines.
- Category Group Visibility misconfiguration hides articles users need. Test as a representative user profile after every visibility change.
- Deleting a category strips the tag from every article that held it. Plan category changes carefully; restructures are operationally heavy.
- The 5-active-group limit binds for highly diverse global operations. Combine dimensions or use secondary categorization via custom fields when the limit binds.
- Articles without category tags do not appear in category-filtered search. Audit coverage quarterly to catch gaps.
- Authors who do not understand the taxonomy tag inconsistently. Training is the difference between a clean Knowledge base and a category mess.
Trust & references
Cross-checked against the following references.
- Data Categories referenceSalesforce
- Knowledge overviewSalesforce
Straight from the source - Salesforce's reference material on Data Categories.
- Data Categories OverviewSalesforce Help
- Set Up Data CategoriesSalesforce Help
- Category Group 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. In which area of Salesforce would you typically find Data Categories?
Q2. Why is understanding Data Categories important for Salesforce admins?
Q3. Can a Salesforce admin configure Data Categories without writing code?
Discussion
Loading discussion…