Freshdesk Solutions (Knowledge Base) Categories & Folders Explained

The three levels: category, folder, article

Everything in Solutions lives inside a fixed parent-child chain. A category is the top level — a broad grouping like "Getting Started" or "Billing & Refunds." Inside a category you place folders, the mid-level buckets that group related articles ("Account Setup," "Installation Guides"). And inside a folder you place the articles themselves — the actual how-tos and FAQs your customers read.

The constraint that trips people up is that an article cannot live directly under a category. It must sit inside a folder. Freshworks makes this explicit in its Manage your Knowledge Base documentation: when you move an article to a different category, the destination category must already contain at least one folder, or there's nowhere for the article to land. So the mental model is simple — categories are shelves, folders are the boxes on those shelves, and articles are what you actually pull out.

Where you create each level. Per Freshworks' Create and organize your Knowledge Base guide, you build all three from the Solutions page. From Solutions → New Article, you get options for New Category, New Folder, and a new article. Folders always ask you to pick a parent, which is what keeps the hierarchy intact.

How deep the tree can go (and the plan that gates it)

For most teams the structure stops at three levels: category, folder, article. But Freshdesk also supports a flexible hierarchy that lets you nest folders inside folders — up to five nested folder levels, which combined with the category gives a six-level structure. That's useful when a single product line needs "Product → Feature Area → Sub-feature → Version" depth rather than a flat list.

Be honest with yourself about the plan cost, though: the multi-level (nested sub-folder) hierarchy is an Enterprise-plan feature. On lower plans you're working with the classic Category → Folder → Article three-level model. That's not a knock — three levels is plenty for the vast majority of help centers, and going deeper often hurts findability more than it helps. But if your content plan assumes four levels of nesting, confirm your plan supports it before you design around it.

Visibility scopes: who can see a folder

This is where Solutions gets genuinely powerful, and where mistakes are most common. Visibility is set at the folder level (and can be bulk-applied to articles), using a "Visible to" control. The scopes Freshdesk exposes are:

• All users — customers, agents, and Freshchat bots. This is your fully public content.
• All agents — visible to agents only, hidden from customers entirely. This is how you keep internal SOPs, escalation playbooks, and canned-response source material out of the public help center.
• Logged in users — only customers who have authenticated into your portal can see it. Ideal for content you'll show to registered users but not anonymous visitors or search engines.
• Companies — restrict a folder to contacts belonging to specific companies (e.g. a named-account runbook).
• Contact segments and Company segments — scope by dynamic groups defined on criteria like plan tier, region, or subscription.
• Bot — surface the folder to Freshchat bots only.

The practical upshot: a single category can mix a public "All users" folder, an internal "All agents" folder, and a gated "Logged in users" folder side by side. Freshworks documents these controls in Restricting the visibility of solution articles. Because visibility is a real access boundary, treat it the way you'd treat any other permission model in your help desk — the same care you'd apply to ticket statuses and workflow states applies here.

Category visibility is a separate lever. Categories are mapped to portals — if you run multiple product portals (a higher-plan feature), you choose which portal(s) a category appears on. So a folder can be perfectly public and still be invisible to a given audience simply because its category isn't published to that audience's portal.

Agent vs customer visibility, and draft vs published

Two different mechanisms decide whether a person sees an article, and conflating them causes most "why can't the customer see this?" tickets.

The first is the visibility scope above (all users, agents-only, logged-in, and so on). The second is the article's status: an article is either a Draft or Published. This matters because draft articles are visible on the agent portal but never to customers — an agent searching from inside a ticket can pull up a half-finished draft as reference, while the public help center shows nothing until you hit Publish. Freshdesk even gives you dedicated list views — All drafts, My drafts, and Published articles — to manage this pipeline.

So an article reaches a customer only when both conditions are true: its folder's visibility scope includes that audience, and the article itself is Published. A published article inside an "All agents" folder is still invisible to customers; a public folder full of drafts still shows customers nothing. When you're auditing a "missing" article, check both dials.

Managing the tree: moving, reordering, and bulk visibility

Once content exists, Freshdesk's two-pane view is where you reshape it. From there you can perform bulk actions — Move To (relocate articles or folders to another category/folder), reorder articles within a folder, and change the visibility of multiple articles at once. The one rule to remember from the Manage your Knowledge Base docs: when moving an article into a different category, that destination category must already own at least one folder, because an article has nowhere to live directly under a bare category.

A sensible way to organize from day one:

1. Create categories around top-level customer intents, not internal team names ("Billing," not "Finance Ops").
2. Inside each, create folders per task or feature, and set folder visibility deliberately — public "All users" for self-serve, "All agents" for internal-only.
3. Keep works-in-progress as drafts so agents can reference them while you finish, then publish in a batch.
4. Reserve the nested (Enterprise) hierarchy for genuinely deep product trees; otherwise stay flat for findability.

The honest limits — and where an AI layer picks up

Freshdesk Solutions is a solid, well-structured knowledge base. The hierarchy is clear, the visibility model is granular, and the draft/published split is a proper editorial workflow. Credit where it's due: as a place to store and organize answers, it does the job.

But notice what a knowledge base fundamentally is — a library, not a librarian. It holds the answers; it doesn't read the customer's specific ticket, decide which of your 300 articles is the right one, and write a tailored reply. Freshdesk's own portal search surfaces articles, but it still asks the customer (or the agent) to do the matching and the synthesis. Structure and visibility scopes govern who can see what; they don't govern whether the right answer actually reaches the person who needs it, phrased for their situation. And an agents-only folder full of perfect internal SOPs still relies on a human remembering it exists mid-conversation.

This is the seam where an AI agent layer fits — and it's worth understanding what AI agents for customer service actually do before reaching for one. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector, and it does not replace your help desk, your Solutions content, or its visibility rules. You connect Macha to Freshdesk with your subdomain and API key, and it reads your published Solutions articles as a grounded knowledge source — then drafts or sends cited answers on real tickets, matching the customer's actual question to the right article automatically. It complements Freshdesk's own automations rather than competing with them, and the broader pattern of automating Freshdesk with AI is exactly this: keep your knowledge base as the organized source of truth, and add a layer that turns it into answers. Where an answer needs live data — an order status, an account tier — a custom tool lets the agent call your own API instead of guessing. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — the pricing page breaks that down.)

The clean division of labour: keep Freshdesk Solutions as the well-organized library — categories, folders, visibility scopes, draft-then-publish — and layer an agent on top to be the librarian that reads each ticket and delivers the right article as a real, cited answer.

FAQ

What is Freshdesk Solutions? Solutions is Freshdesk's built-in knowledge base. It organizes self-service content into a three-level hierarchy — categories hold folders, and folders hold the articles customers and agents read.

Can I put an article directly under a category in Freshdesk? No. Articles must live inside a folder. When you move an article to a different category, that destination category has to already contain at least one folder, or there's nowhere for the article to go.

How many folder levels does Freshdesk support? The standard structure is Category → Folder → Article (three levels). Freshdesk also offers a flexible hierarchy with up to five nested folder levels (a six-level structure overall), but that multi-level nesting is an Enterprise-plan feature.

What are the folder visibility options in Freshdesk? Folders use a "Visible to" control with scopes including All users (customers, agents, and Freshchat bots), All agents (agents only), Logged in users (authenticated portal users), specific Companies, and Contact/Company segments. Category visibility is set separately, per portal.

What's the difference between a draft and a published Freshdesk article? Draft articles are visible on the agent portal but never to customers, so agents can reference works-in-progress. An article only reaches a customer when it's Published and its folder's visibility scope includes that audience.

Ready to turn your organized Solutions content into cited answers on every ticket? Start a free trial of Macha and connect it to your Freshdesk in minutes.