What we do
Tools
Industries
Department
How we workLet's talk →
Home/Service Cloud/Salesforce Knowledge Base
Service Cloud

Salesforce Knowledge Base: Setting It Up, and Keeping Every Article True

Service Cloud is live, and the answers agents actually use are in a shared drive of Word docs and one senior agent's head. Moving them into Salesforce Knowledge puts articles on the case, in the console and on your help site. Before you create the first one, decide who it's for, because that choice shapes the rest of the setup.

Setting up Lightning Knowledge, in order

Run this in a sandbox first. A couple of these steps are hard or impossible to undo.

  1. 1

    Give yourself the Knowledge User license

    Setup Users Edit Knowledge User

    Authors and admins need the Knowledge User feature license ticked on their user record before Knowledge settings will open. Whether your org has those licenses, and how many, depends on your edition and contract, so look at Company Information before planning who writes.

  2. 2

    Turn on Lightning Knowledge

    Setup Knowledge Settings

    Enable Knowledge, then Lightning Knowledge. Articles become records of a standard Knowledge object, with versions that move from draft to published to archived.

    Watch for: once Lightning Knowledge is on, it can't be switched off. Orgs still holding Classic Knowledge articles need a migration plan first.

  3. 3

    Create article record types

    Setup Object Manager Knowledge Record Types

    One per kind of article, such as FAQ, troubleshooting or policy, each with its own page layout and fields. Keep the list short. Authors choose the type every time they write.

  4. 4

    Build data categories and set who sees them

    Setup Data Category Setup

    Category groups (product line, region, audience) hold a tree of categories. Visibility is granted separately for agents, customers and partners, and it's the most common reason a published article doesn't show up.

  5. 5

    Add approvals if articles need sign-off

    Setup Approval Processes Knowledge

    An approval process on Knowledge routes a draft to a reviewer before it can be published. Useful for policy and legal articles, and usually overkill for quick fixes.

  6. 6

    Add Knowledge to the case page

    Lightning App Builder Case record page Knowledge

    The Knowledge component on the case searches articles from the case details, and agents can attach the one that solved it. Those attachments are how you'll later see which articles earn their keep.

Articles agents stop trusting, and why

The article quotes a fact another system owns

How you'll know: A price, a warranty term or a firmware version in the article is out of date, and agents quietly correct it on the phone.

Fix: Store that fact in its own field and fill it from the product catalog, billing system or policy table, or flag the article for review the moment the source changes. Knowledge has no way to notice the change by itself.

Published, but nobody can find it

How you'll know: The article shows as published in Salesforce, yet it's missing from the help site or the agent's search.

Fix: Check the channel boxes on the article and the category visibility of the people who should see it. It's nearly always one of the two.

Suggestions on cases look random

How you'll know: Agents ignore the Knowledge panel and search by hand, because the top results rarely match the case.

Fix: Tighten article titles and summaries around the words customers use in case subjects, and categorize consistently. Adding the customer's product and plan to what's searched helps more than adding articles.

Who reads the article, and which channel that means

Each Knowledge article is published to one or more channels. Tick the wrong one and the right people never see it.

Reader Channel Plan for
Agents working cases in the console Internal App Internal steps, escalation notes and workarounds that should never reach a customer. Keep those on a record type or category that's never published outward.
Logged-in customers on an Experience Cloud site Customer Customers only see categories their site profile has visibility to, so a published article can still be invisible.
Resellers or service partners on a partner site Partner Partners often need install and pricing detail customers shouldn't get. Separate categories make that manageable.
Anyone on the web, with no login Public Knowledge Base Search engines index these. Anything time-sensitive on a public article is the first thing to go stale in public.

Questions people ask

What is Salesforce Knowledge?

It's the knowledge base built into Salesforce. Teams write, categorize and publish articles that agents see on cases in Service Cloud and that customers or partners can read on an Experience Cloud site or a public help center. Current orgs run it on the Lightning Knowledge model.

Is Salesforce Knowledge included with Service Cloud, or is it a separate license?

It depends on your edition and what's on your contract. Anyone writing or managing articles needs a Knowledge User feature license, and some editions include those while others sell them separately. Company Information in Setup shows what your org has.

What's the difference between Lightning Knowledge and Classic Knowledge?

Classic Knowledge used separate article types, each its own object. Lightning Knowledge puts every article on one Knowledge object and uses record types to tell them apart, which is simpler to report on and to extend. Switching to Lightning Knowledge is permanent once it's enabled.

Does Salesforce Knowledge automatically suggest articles on a case?

Yes. With the Knowledge component on the case page, articles are searched from the case details and shown to the agent, who can attach the one used. How good those suggestions are comes down to titles, categories and whether the content is still right.

Can Salesforce Knowledge pull in data from outside systems automatically?

Not by itself. Article content is typed and updated by people. n-frames builds the integration that fills specific article fields from the system of record, or opens a review when that record changes, using Salesforce's APIs and Flow where it fits.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.