Category, Solutions
A Category for Solutions, usually called a Solution Category, is a label in the older Salesforce Solutions feature that groups similar Solution records into a browsable hierarchy.
Definition
A Category for Solutions, usually called a Solution Category, is a label in the older Salesforce Solutions feature that groups similar Solution records into a browsable hierarchy. Each Solution is a documented answer to a recurring customer issue. Solution Categories let support agents and customers find the right answer by walking a category tree instead of relying only on keyword search. A single Solution can sit in more than one category.
This is a legacy taxonomy. The Solutions feature predates Salesforce Knowledge and shipped with the earliest Service Cloud releases. Solutions and their categories are not available in Lightning Experience as a primary feature, and Salesforce now steers new service work to Lightning Knowledge. Knowledge uses Data Categories and Data Category Groups to do the same organising job with more flexibility. The Solution object still exists and stays queryable in older orgs, so the term shows up in pre-2020 documentation, certification material, and partner blogs.
How Solution Categories shaped the old Solutions feature
What a Solution record actually is
Before you can categorise anything, it helps to know what a Solution is. A Solution is a standard Salesforce object that holds a detailed description of a customer issue and the resolution for that issue. The two fields that carry the weight are the solution title and the solution note, which is the body text agents read when they want to resolve a Case. Solutions also track a status (for example Draft or Reviewed), a flag for whether the content is published, and a flag for whether it is public. Agents attach a Solution to a Case so the same answer can be reused across many similar tickets. Salesforce records that link in a separate join object, so one Solution can be tied to many Cases and one Case can reference several Solutions. This reuse model is the whole point of the feature. Instead of every agent writing the same answer from scratch, the team builds a shared library once. Solution Categories then sit on top of that library as the navigation layer, which is why the two concepts are almost always discussed together.
The All Solutions tree and the category hierarchy
Solution Categories form a single hierarchical tree for the whole org. At the top sits a category called All Solutions, which Salesforce creates automatically. You cannot file a Solution directly under All Solutions, and you cannot translate that top node. Everything you build hangs beneath it as nested subcategories. An admin shapes the tree in Setup, naming each category, choosing its parent, and setting whether children sort alphabetically or in a custom order. The structure mirrors how a support team thinks about its product, so a billing team might have a Billing branch with Invoices and Refunds underneath. Depth is a judgement call. A tree that is too flat forces long category lists, and a tree that is too deep makes agents click through many levels. Because there is only one tree per org, every team shares the same taxonomy, which is one of the limitations that later pushed Salesforce toward the richer Knowledge model. Backslash characters are not allowed in category names, a small rule that trips up people importing names from other systems.
Assigning a Solution to its categories
Categorising a Solution happens on the Solution record itself, not in Setup. An author opens the Solution, finds the Solution Categories related list, and clicks Select Categories. That opens the same hierarchy the admin built, where the author clicks Select next to each category that fits and Deselect to remove one. Saving writes those assignments. To do this an author needs the Edit permission on Solutions, and administrators or users with the Manage Categories permission can categorise solutions even before the feature is switched on for everyone. Salesforce advises restraint here. The official guidance is to file a Solution only in its most relevant categories, because over-tagging makes content harder to find rather than easier. There is a helpful detail for multilingual orgs. When a master Solution is translated, the translated versions automatically inherit the categories of the master and stay synchronised with it. That keeps a Spanish answer and its English original in the same place in the tree without an author having to re-tag each language by hand.
Turning on browsing and where categories appear
Assigning categories does nothing visible until an admin turns on solution category browsing for the Solutions tab. Once that switch is on, the category tree becomes a navigation panel. Agents browse down the branches and see the Solutions filed in each node, which is faster than guessing keywords when they already know the rough area of a problem. The same categorised content can surface in several places beyond the internal tab. Categories show up during Case resolution, where an agent looking at a Case can browse for a matching answer. They also drive public-facing channels. Solutions marked public could appear in the old Self-Service Portal and the Customer Portal, letting customers browse the same tree and deflect Cases by finding answers themselves. Those portals are themselves legacy now, replaced by Experience Cloud sites, but in the Solutions era they were the self-service front end. One operational note from the docs: you cannot delete a category that a Customer Portal is using, so cleanup has to follow the right order.
Why Salesforce moved to Knowledge and Data Categories
Solutions were simple, and that simplicity became their ceiling. A Solution note is largely plain text with limited formatting, the search experience is basic, and the single category tree cannot express more than one way of slicing content. Salesforce Knowledge, and now Lightning Knowledge, answers all three gaps. Knowledge articles support rich text, files, multiple article types, and version history. Search is stronger and tuned for self-service. Most importantly, Knowledge replaces the single Solution tree with Data Category Groups, where an org can run several parallel taxonomies at once. A product might be classified by region in one group and by product line in another, and the same article can be tagged in both. Data Categories also tie into article visibility, so different profiles and roles can see different slices of the library. That access control simply did not exist for Solution Categories. Because of these advantages, Salesforce stopped investing in Solutions and now documents Knowledge as the supported path. New orgs do not lead with the Solutions UI, and the feature is absent from Lightning Experience as a headline capability.
Migrating from Solution Categories to Data Categories
Teams still running on Solutions usually plan a move to Knowledge rather than staying put. There is no single turnkey button for this. The common pattern is to export the Solution records, reshape the title and solution note into Knowledge article fields, and import them as articles tagged against the matching Data Categories. The category tree itself often needs rethinking during the move, because Knowledge lets you split one overloaded Solution tree into several focused Data Category Groups. Treat that as an upgrade rather than a copy. The part teams forget is the Case history. Cases that pointed at Solutions need to point at the equivalent Knowledge articles, or the resolution trail behind closed Cases is lost. It is wise to keep the old Solution data queryable until the new Knowledge content is verified, then retire the Solutions tab from agent layouts so nobody works in two systems at once. Salesforce publishes migration guidance and the Lightning Knowledge setup steps, but expects the data transformation itself to run through export, mapping, and import.
Reading the term in older documentation today
The practical reason to understand Category for Solutions in 2026 is translation. The phrase appears across pre-2020 Salesforce documentation, older certification study guides, and a large body of partner blog posts from the 2008 to 2018 window when Solutions was a mainstream Service Cloud feature. When you hit it, mentally map Solution Categories to Knowledge Data Category Groups and map Solution records to Knowledge articles. The underlying intent is identical: organise a library of canned answers so people can find them quickly. Only the product and the flexibility differ. If you are auditing an inherited org and find a populated Solutions tab with a deep category tree, that is a clear signal the org skipped a Knowledge migration. It is not broken, and the data is safe, but it receives no new platform investment. Plan the migration before building anything new on Solutions, and use the existing category tree as a head start for designing the Knowledge Data Categories that will replace it.
How Solution Categories were set up in Salesforce Classic
Solution Categories are built in Salesforce Classic Setup, then switched on for the Solutions tab. This reflects how the legacy feature was configured; new orgs should set up Lightning Knowledge with Data Categories instead.
- Open Solution Categories in Setup
From Setup, type Solution Categories into the Quick Find box and select it. You see the hierarchy with the auto-created All Solutions category at the top. You need the Manage Categories permission to edit the tree.
- Add categories and subcategories
Click Add Category to create a node, give it a name (no backslash characters), pick a parent category, and choose alphabetical or custom sort order for its children. Repeat to build out the branches your support team needs.
- Categorise individual Solutions
Open a Solution record, find the Solution Categories related list, and click Select Categories. Click Select next to each fitting category, Deselect to remove one, then Save. File each Solution only in its most relevant categories.
- Turn on category browsing
Enable solution category browsing for the Solutions tab so agents and, where configured, portal users can navigate the tree. For public answers, enable public solutions so the categories appear in the relevant self-service channel.
The label shown in the tree. Backslash characters are not allowed, and All Solutions cannot be renamed or used to file Solutions directly.
Where the new category sits in the hierarchy. Choosing All Solutions places it at the top level; choosing another category nests it underneath.
Whether child categories list alphabetically or in a custom order you define, which controls how agents see the branch.
The org-level switch that makes the category tree appear on the Solutions tab. Without it, category assignments exist but are not browsable.
- Solutions and Solution Categories are a Salesforce Classic feature and are not available in Lightning Experience as a primary capability. Configure Lightning Knowledge with Data Categories for new work.
- You cannot delete a category that a Customer Portal is using. Remove the dependency first, then delete the category.
- Categorising a Solution requires the Edit permission on Solutions, and editing the tree requires Manage Categories. Missing either permission blocks the respective step.
- Translated Solutions inherit categories from their master Solution automatically, so do not try to re-tag each language version by hand.
Prefer this walkthrough as its own page? How to Category, Solutions in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Categorize SolutionsSalesforce
- Defining Solution CategoriesSalesforce
Straight from the source - Salesforce's reference material on Category, Solutions.
- Solution | Object Reference for the Salesforce PlatformSalesforce
- Categorize SolutionsSalesforce
Hands-on resources to go deeper on Category, Solutions.
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 are Solution Categories used for in Salesforce?
Q2. Is Solutions a current Salesforce feature or a legacy capability now?
Q3. What should you do with Solution Categories during a Knowledge migration?
Discussion
Loading discussion…