Category Group for Answers
A Category Group for Answers was the container that held a hierarchy of Data Categories for the legacy Answers feature in Salesforce.
Definition
A Category Group for Answers was the container that held a hierarchy of Data Categories for the legacy Answers feature in Salesforce. Answers was a Classic question-and-answer tool, built on the Question standard object, where members of an answers community (also called a zone) posted questions and the crowd replied. The Category Group supplied the browsable taxonomy. Members narrowed by a top-level category, read related questions, and an admin could mark the best reply. Each org assigned one Category Group to its answers community so every question in that zone shared the same category tree.
This is a retired, legacy term. Per Salesforce, starting in Summer 13 the Answers feature was no longer available in new orgs, and the related Chatter Answers product was closed to new orgs in Summer 16. The modern replacement is Chatter Questions, released in Winter 15 and built on Feed Post and Feed Comment objects, which uses Topics instead of a Data Category hierarchy. The underlying Category Group and Data Category infrastructure still exists and powers Salesforce Knowledge categorization today, so the plumbing survives even though the Answers surface that consumed it is gone.
From answers zones to Chatter Questions: the life of a Category Group
What a Category Group actually was
A Category Group is a named container that holds one tree of Data Categories. Think of the group as one dimension of a taxonomy, such as Products or Regions, and the Data Categories inside it as the branches and leaves. For the Answers feature, an admin built the group under Setup, then assigned it to the answers community so questions could be filed against its categories. The group did not store content itself. It stored the structure that content was tagged against. Salesforce sets default ceilings here that are worth remembering. An org can create up to five Category Groups and keep three of them active at once. Each group can hold up to 100 Data Categories and go up to five levels deep. Those same limits applied whether the group fed Answers, Knowledge articles, or Ideas, because all three shared the identical Data Category engine. The Answers feature simply pointed at one group and inherited its tree. That shared design is the reason the term still echoes through current Knowledge documentation, where Category Groups remain a daily configuration object.
The first-level-only rule on the Answers tab
Answers had a quirk that tripped up many admins. On the Answers tab, only first-level Data Categories displayed to members. The deeper branches of the tree were invisible in the answers community even though they existed in the group. Salesforce documentation is explicit about the workaround. When you build categories for a portal or community answers zone, the categories you want members to see must sit in a sibling relationship, not a parent-child relationship. In plain terms, you flatten the part of the tree that the community browses. A Knowledge article could happily use a five-level hierarchy, but the same group exposed to Answers only ever showed its top row. This is one of the cleaner illustrations of why Answers and modern Q&A diverged. Chatter Questions dropped the hierarchy entirely in favor of flat Topics, which sidesteps the first-level limitation by never having levels in the first place. Anyone reading old setup notes that warn about sibling categories is looking at Answers-era guidance, not anything that applies to a current Chatter Questions or Experience Cloud build.
Sharing one group across Answers and Knowledge
Salesforce explicitly allowed Answers and Knowledge articles to use the same Category Group. The official guidance even suggested a split. If an org ran both, you might dedicate one group to the answers site and two more to articles, staying inside the active-group ceiling. The payoff was a single taxonomy across self-service questions and the official article library. A member browsing the answers community under Routers saw peer questions, and the same Routers branch in Knowledge surfaced vetted articles. Category visibility was governed by the same Data Category Visibility settings used for Knowledge, so a partner profile and a customer profile could each see a tailored slice of the tree. Admins usually managed both in one place because the model was shared. This overlap is also why migrating off Answers rarely meant losing the taxonomy itself. The Category Groups kept working for Knowledge. What went away was the Answers surface that let members browse questions by category. The categorization scheme could be preserved on the article side while the Q&A experience moved to a different model.
Why the Answers feature was retired
Salesforce ran three generations of question-and-answer tooling. The first was Answers, built on the Question standard object and reachable only through the Answers tab in Salesforce Classic. The second was Chatter Answers, a richer Classic experience that combined questions, Knowledge, and cases, also built on the Question object. The third and current generation is Chatter Questions, released in Winter 15 and built on Feed Post and Feed Comment objects. Running three overlapping products was not sustainable, so Salesforce closed the older ones to new orgs. Answers stopped being available in new orgs starting in Summer 13. Chatter Answers stopped being available in new orgs starting in Summer 16. Both decisions pushed customers toward the Chatter-native model. The retirement was less a sudden switch-off and more a long sunset. Existing orgs that had already enabled Answers could keep their data, but new orgs never got the feature, and Salesforce steered every new self-service build toward Chatter Questions and Experience Cloud. By the time an admin meets the phrase Category Group for Answers today, it is almost always inside legacy documentation or an old org rather than a live configuration screen.
What replaced it and how categorization changed
Chatter Questions is the modern answer, and it categorizes content very differently. Instead of a Data Category hierarchy attached through a Category Group, Chatter Questions relies on Topics. Topics are flat labels with no parent-child nesting. A member tags a question with one or more Topics, and Experience Cloud surfaces let visitors filter by Topic. The trade is real. You gain a lighter, Chatter-native experience that lives in feeds and on Experience Cloud pages, and you lose the structured, multi-level browsing that a Category Group provided. Many teams bridge the gap by keeping a rich Data Category hierarchy on the Knowledge side, where Category Groups still apply, while running the conversational Q&A layer on flat Topics. That hybrid keeps deep, drill-down navigation for official articles and a fast, social posting flow for community questions. The two systems no longer share one taxonomy the way Answers and Knowledge once could, so information architecture for a modern community usually treats Knowledge categorization and Q&A tagging as separate exercises with separate models behind them.
The data and reporting left behind
Orgs that enabled Answers before the sunset can still hold legacy data. Questions and replies were stored against the Question and Reply objects, tagged to Data Categories from the assigned Category Group. Those records remain queryable, and the Category Group itself stays visible in Setup for orgs that had it. The catch is that anything built on this legacy shape does not carry over to Chatter Questions. A report that filtered legacy Answers questions by Category Group will not describe Chatter Questions activity, because Chatter Questions lives on Feed Post and Feed Comment records and tags with Topics rather than categories. Rebuilding that reporting means pointing at the feed-based objects and filtering on Topics, which is a genuinely different schema. Teams doing this cleanup usually inventory the old Answers reports, decide which metrics still matter, and recreate them against the new model rather than trying to convert them in place. The reporting surface for Q&A also tends to be narrower under the Chatter model, so some legacy dashboards simply do not have a one-to-one equivalent.
Where you still meet the term
Category Group for Answers shows up mostly in material written before the sunset. Pre-Summer-13 admin guides, older certification study notes, partner blog posts, and long-lived internal runbooks all reference it. Current Salesforce Help no longer documents Answers as a feature you would set up fresh, so any live mention you find is effectively historical. The safest reading is to translate on sight. When a document says Category Group for Answers, mentally map it to two modern ideas. The hierarchical categorization concept lives on as Data Category Groups for Knowledge, configured under Data Category Setup. The community question-and-answer concept lives on as Chatter Questions with Topics, surfaced through Experience Cloud. Keeping that translation handy saves a lot of confusion, especially for newer admins who will never see an Answers tab. If you maintain your own documentation, it is worth a pass to update Answers-era language so future readers are not sent looking for a configuration page that no longer exists for them.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Category Group for Answers.
- Create and Modify Category GroupsSalesforce
- Work with Data CategoriesSalesforce
Hands-on resources to go deeper on Category Group 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 is a Category Group for Answers?
Q2. Is Answers still an active Salesforce feature?
Q3. What is the modern replacement for Answers?
Discussion
Loading discussion…