Freshdesk Knowledge Base: Portal Setup and Plan Gates (2026)

Freshdesk includes a knowledge base and customer portal on every plan; the plan decides upkeep. Growth gives you a three-level library, a portal on your own domain with free SSL, and articles auto-suggested on the ticket form. Pro adds translations, templates, versioning, bulk edits and up to five product portals; Enterprise adds approval workflow and six levels. Start on Growth for one language and one product. Freshdesk's pricing page lists Growth at $19 per agent per month billed annually, or $23 per agent per month billed monthly^[1]. Billing is per agent and every agent on the account sits on the same plan, as our Freshdesk pricing guide explains.

Build the library first: categories, folders, articles

Every current plan organizes content as category, then folder, then article, and the help center sets no limit on how many of each you create. Categories are the top shelves, such as Billing or Shipping, and folders group related articles under them. Visibility is set per folder: all users, logged-in users, agents, selected companies, or bots. Folders can also be limited to customer segments, which lets you show contract terms only to the accounts they apply to. Attachments can reach 25 MB each and 100 MB per article, and inline images are capped at 5.2 MB.

Getting an existing library in is the slow part. Freshdesk's help center describes one import route: you email a CSV of your articles to its support team, who check and process it. Articles can also be created through the API from Growth up, and inline images come through that way only when they are hosted at a public address. A new account gets a 14-day trial with Enterprise features and no card; when it ends you pick a plan or the account is suspended. Since the trial runs on Enterprise features, keep to three levels and one language if you plan to buy Growth. Plan the import early, because a migration of a few hundred articles that depends on a support queue can easily outlast that window.

Roles matter from day one. Every agent, whatever the role, can create solution articles as drafts, while publishing and editing rights sit in the Solutions permissions of each role; custom roles that fine-tune those rights are a Pro feature. Collaborators, the free seats Pro adds for experts outside the support team, cannot edit solution articles. Shared agents from Freshsales cannot edit the knowledge base either. In practice the people who write articles need agent access, either a full-time seat or occasional-agent day passes, which matters when you count licenses.

Growth, Pro or Enterprise: what each plan adds to the knowledge base

The library itself never changes between plans. What changes is how you maintain it, how many audiences it serves and how much you can measure. A one-language team on one brand can stay on Growth for years; a team translating content or running two brands cannot. The table lists the gates we read in Freshdesk's help center and pricing page^[2].

Pro is the expensive step. At the annual rates, Pro costs $660 per agent a year against $228 on Growth, a gap of $432 per agent a year by our arithmetic, and $516 per agent a year when both are billed monthly. Because every agent sits on the same plan, a ten-agent team pays that gap ten times, $4,320 a year on annual billing, even if only two people write articles. Enterprise adds another $408 per agent a year over Pro on annual billing. Multilingual content is usually what forces the first upgrade; reviewers who must sign off before publishing are what force the second.

Set up the customer portal your articles live in

The portal is where articles meet customers: a branded site to raise and track tickets, read the knowledge base and, from Pro, post in community forums. By default anyone can submit requests and read articles without logging in. The Who can view solutions setting, under Admin, Channels, Portals, Settings, closes the library to signed-in users. New accounts get the Marina theme, built to WCAG 2.0 AA. From Growth you can point your own domain at the portal with a CNAME record; Freshworks then issues a free certificate within 24 hours, and wildcard certificates are not supported.

Settle the subdomain before launch. Renaming the yourcompany.freshdesk.com subdomain takes effect immediately, logs agents out and breaks inline images in existing tickets, ticket status links, and every knowledge base and forum link already in circulation. Old links in emails, macros and your product's help menu then lead customers to error pages. Ideally set up the custom domain before the first article goes public too.

Pro changes how much of the portal you can shape. You get the theme code itself (HTML, CSS, JavaScript and the Liquid templating engine, version 2.4.1), control over which portal sections appear, and multiple products. Each product gets its own portal, URL, mailbox and knowledge base, with up to five products on Pro and no cap on Enterprise. A single category can be shown across several product portals, so shared articles such as account security need writing only once. On Enterprise, Workspaces, which Freshworks switches on by request, also scope the knowledge base to each workspace.

Keep articles current as the library grows

The cheapest source of articles is your agents' best replies. Add kbase@yourcompany.freshdesk.com in BCC on a reply and Freshdesk saves it as a draft solution article, on every plan. Drafts autosave, though changes to article properties and attachments do not, and deleting a draft cannot be undone. From Growth the editor adds a table of contents and suggestions for linking related articles. Each article carries an SEO title, description and keywords; the help center recommends 50 to 60 characters for the title and 150 to 160 for the description.

On Pro, templates (up to 30 per account, one of which can load by default) keep structure consistent across writers. Versioning saves a version on every save or publish, highlights changes in green and red, and restores an old version as a new one; formatting-only edits are not highlighted. Bulk actions change authors and tags, export articles or send a batch for review. Enterprise adds the approval workflow, where a draft is sent for review, approved and then published, with status tracking and notifications to approvers^[3]. It also unlocks six levels of hierarchy: categories, then folders and sub-folders five deep.

Running a multilingual knowledge base

Translation is a Pro feature. Once you add a secondary language, it stays hidden on the portal until an admin makes it visible. Translations can be created only after the master article exists in the primary language, and each translation can carry its own tags, folder names and category names. Editing the master does not flag translations by itself: someone has to use the Mark other translations as outdated option, and the outdated view appears only when a secondary language is selected. Choose the primary language carefully. Admins cannot change it after multilingual support is on; only Freshdesk support can, from the backend.

Make the articles deflect tickets and feed the AI

Deflection starts on the ticket form. From Growth, the portal suggests articles from the subject while a customer types, and agents see a customer journey showing which articles the customer opened before writing in, with a warning if they insert one already viewed. On every plan, Suggested Solutions lists matching articles beside each ticket, and agents can insert one into a reply as a link or as full content, provided it is visible on the portal. A dislike on a published article opens a feedback ticket, so weak articles surface in the queue.

The help widget on standalone Freshdesk is a lite version with the knowledge base and web forms only; live chat in the widget belongs to Freshdesk Omni. The widget can show the contact form only after an article fails to help. Appearance changes start on Growth, while contextual articles tied to pages of your site, up to five per URL, need Pro. The agent apps for iPhone, iPad and Android search solution articles too, so agents can insert them on the move.

The same articles feed Freddy AI. The Email AI Agent, available from Growth, answers new email, portal and web-form tickets from solution articles and other knowledge sources. It reads only published articles whose visibility is all users or bots; private and restricted articles are excluded^[4]. Freddy AI Agent includes 500 sessions once per account, which last until used, then charges $49 per pack of 100 sessions, added to the current billing cycle. Unused purchased sessions do not carry over to the next cycle, and at zero the AI agent stops answering. Our Freshdesk AI playbook covers the meters.

Copilot is the agent-side add-on, and it never uses sessions. Freshdesk's pricing page lists the Freddy AI Copilot add-on, Pro and Enterprise only, at $29 per agent per month billed annually or $35 per agent per month billed monthly; Freshdesk can auto-assign unassigned licenses unless you opt out. Copilot drafts new articles, and suggests existing ones inside tickets once you have about 25 published.

Measuring needs Pro. The knowledge base dashboard shows article counts, drafts, views, likes and dislikes; curated reports cover an overview, article insights and agent performance over a default 29 days; and custom reports track views, feedback tickets and articles suggested, created and published. The help center lists the automatic sitemap, generated at /support/sitemap.xml and refreshed every Sunday, among Pro and Enterprise features. On Growth, the Google Analytics app sends portal traffic to Google Analytics, but those numbers stay there and never appear inside Freshdesk.

The bottom line

Freshdesk's knowledge base is solid on every plan, and Growth covers a single-language library on one portal with auto-suggest, a custom domain and articles that feed the Email AI Agent. The upgrade decision is about upkeep, not the library. Pro earns its higher per-agent price when you translate content, run several brands or need versioning and reports, and Enterprise only when articles need formal approval. Fix your subdomain, folder visibility and import route during the trial, because those choices are the hardest to undo later.