Data Category for Answers
A Data Category for Answers was a label, drawn from a Data Category Group, that the legacy Salesforce Answers and Chatter Answers features used to classify a customer question by topic.
Definition
A Data Category for Answers was a label, drawn from a Data Category Group, that the legacy Salesforce Answers and Chatter Answers features used to classify a customer question by topic. When a person posted a question in a public portal or community, they tagged it with a category. Other people could then browse or filter questions by that category, and topic experts could subscribe to a category to be notified when new questions arrived in their area.
This is a retired concept. The standalone Answers tab and Chatter Answers were both removed by Salesforce; Chatter Answers retired after the Winter '18 release, and orgs created on Summer '16 or later never received it. The replacement is Chatter Questions, surfaced inside Experience Cloud sites, which organizes content with Topics instead of Data Categories. Data Categories themselves are still very much alive, but only for Salesforce Knowledge, not for any Answers experience.
How Answers used Data Categories, and why that wiring went away
Where the category came from
Every Data Category for Answers lived inside a Data Category Group, which is an admin-defined hierarchy of labels. A group named Products might hold categories like Laptops, Phones, and Tablets, with finer categories nested beneath. The admin built the group once in Setup, then assigned it to the Answers feature so the community could use it. When someone asked a question, the posting form showed the category picker sourced from that single assigned group. The person chose the label that best matched their question, and Salesforce stored that choice on the Question record as its category. The same Data Category Group could also back Salesforce Knowledge, so one taxonomy classified both questions and articles. That sharing was deliberate. It meant a Best Answer chosen on a question could be promoted into a Knowledge article that already carried a matching category, keeping the two content types aligned under one vocabulary. Visibility settings on the group controlled which roles and license types saw which categories, so internal agents and external portal users could see different slices of the same tree.
The first-level-only display rule
The Answers tab had a quirk that tripped up many admins. It displayed only the first level of categories from the assigned group. If you built a deep parent-child hierarchy, the children simply did not appear as browseable filters on the tab. The practical guidance from Salesforce was to give the categories you wanted visible a sibling relationship rather than a parent-child one. So for an Answers community you flattened the design: the labels users needed to pick sat side by side at the top level, not buried two or three layers down. This is the opposite of how Knowledge prefers categories, where deep hierarchies help authors tag articles precisely. The conflict was a real source of friction when one Data Category Group served both features. Admins often kept the meaningful Answers labels at the top and pushed Knowledge-only refinements into child categories that the Answers tab would ignore. Understanding this rule explains a lot of the awkward category trees still sitting in older orgs that once ran the Answers feature.
What browsing and subscribing actually did
On the live community, the category acted as the primary way to find related discussion. A sidebar listed the available categories, and selecting one filtered the question list down to posts tagged with it. A customer hunting for a known issue could pick the matching category instead of scrolling the entire feed. Category subscription was the feature that made experts useful. A support agent or power user subscribed to the category that matched their specialty, and Salesforce notified them whenever a new question landed there. That turned a passive forum into something closer to a routed queue, where the right person saw the right questions without manual triage. The category also fed search relevance, so a search scoped to a category returned tighter results. None of this required code; it was configuration plus the user's choice at posting time. The weakness was rigidity. A question fit exactly one branch of one group, and reclassifying meant editing the record. There was no easy way to apply several cross-cutting labels to a single question the way modern tagging allows.
Why Salesforce retired the Answers experiences
Chatter Answers was an early attempt at a public, self-service Q and A community, but it never became a strong product. The interface felt dated, customization was thin, and the broader Community Cloud, now Experience Cloud, grew into a far more capable platform for the same goal. Rather than keep two overlapping answers tools alive, Salesforce moved its investment to Experience Cloud and wound Chatter Answers down. The retirement was staged. New orgs on Summer '16 or later did not get Chatter Answers at all, and existing customers were told they could keep using it until their subscription term ended, with Chatter Answers fully retiring after Winter '18. Salesforce was explicit that data could be lost if it was not migrated before the feature went away, and that community pages configured to show answers data would stop appearing. The clear message was to plan a move to Chatter Questions inside an Experience Cloud site well ahead of the cutoff rather than waiting for the lights to go out.
Topics replaced categories for community questions
The replacement feature, Chatter Questions in Experience Cloud, does not use Data Categories to organize questions. It uses Topics. A Topic is a flat, tag-style label that members or admins apply freely to questions, posts, and articles, and a single item can carry several Topics at once. That flexibility addresses the old rigidity directly. A question about a billing error on a mobile app can carry a Billing Topic and a Mobile Topic together, something the single-branch Data Category model could not do. Topics also power Experience Cloud navigation and search, surfacing related questions and articles under a shared Topic page. For anyone building a new self-service community, this is the model to learn. Data Categories remain the right tool when the job is classifying Salesforce Knowledge articles for entitlement-based visibility, because that use case genuinely needs the hierarchy and the role-based access controls. For community Q and A, Topics won, and the Data Category for Answers concept retired alongside the feature that depended on it.
Legacy orgs, leftover metadata, and migration
Orgs that ran Answers or Chatter Answers before 2018 can still hold Question records and the Data Category Groups that classified them. The records often remain queryable through the API even though the browsing UI is gone, so the data has not necessarily vanished. What disappeared is the live experience: the tab, the category sidebar, and the subscription notifications. Admins inheriting such an org should treat any Answers-era category configuration as historical, not active. Reusing that old group for a new purpose tends to cause confusion, because its design was shaped by the first-level-only display rule and other retired behaviors. A real migration to Experience Cloud means re-tagging the worthwhile content with Topics, importing the questions worth keeping into the new site, and archiving the rest. Most teams migrate selectively, lifting the high-value FAQ-style questions and leaving stale threads behind. Documenting that this schema is a relic, and why, saves the next admin from trying to configure a feature that no longer exists in the platform.
Why the term still shows up in study material
Salesforce training content produced between roughly 2010 and 2017 referenced Data Categories for Answers heavily, because the Answers feature was a standard part of the Service Cloud story at the time. Older certification guides, community blog posts, and recorded courses still mention it, so anyone learning from dated material will run into the phrase. The honest takeaway is short. Recognize it as a retired-feature concept, know that Data Categories now belong to Knowledge, and know that community questions are organized with Topics in Experience Cloud. If you see Data Category for Answers framed as a current configuration step, the source is out of date. Keeping that distinction straight prevents wasted effort and keeps your own documentation trustworthy, especially when a teammate or successor relies on it to understand what an inherited org actually supports today.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Data Category for Answers.
- Work with Data CategoriesSalesforce
- Enable Chatter Questions in Your Experience Cloud SiteSalesforce
Hands-on resources to go deeper on Data Category for Answers.
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 was a Data Category for Answers in legacy Salesforce?
Q2. Is the Salesforce Answers feature using Data Category for Answers still supported today?
Q3. What is the modern Salesforce replacement for the legacy Answers feature today?
Discussion
Loading discussion…