Enabling Salesforce Knowledge is a deliberate setup with license, record type, data category, and channel decisions. Done well, the org gets a deflection engine. Done in a hurry, the org gets thousands of unfindable articles.
- Enable Knowledge in Setup
Setup, Knowledge Settings, Edit, check Enable Lightning Knowledge. This is a one-way switch in new orgs and cannot be reversed. Confirm with leadership before flipping it. The setting also enables related objects: KnowledgeArticleVersion, KnowledgeArticleVote, KnowledgeArticleViewStat.
- Assign Knowledge User feature licenses
Open the user record for every internal author and editor. Check Knowledge User. Without this flag, the user cannot create or edit articles even if their profile grants object permissions. The flag is a feature license, separate from the Service Cloud user license.
- Design record types and page layouts
Create record types on KnowledgeArticleVersion for each article variant: FAQ, How-To, Known Issue. Each gets a page layout with the right field set. Keep the list to four or five record types. One record type per team is an antipattern.
- Configure data category groups
Setup, Data Categories, New. Build the hierarchy carefully. Categories are referenced in visibility settings and cannot be deleted if articles use them. Two category groups (one for product, one for audience or region) covers most needs.
- Set Data Category Visibility on profiles
For each profile that needs Knowledge access, open Data Category Visibility and explicitly choose the categories the profile can see. Default visibility (All) is rarely the right choice and silently leaks internal articles to external users.
- Add the Knowledge component to the Service Console
Open the Service Console app, edit a case Lightning record page, drag the Knowledge component into the right rail. Configure auto-suggestion to search article suggestions against the case Subject and Description.
- Publish the first articles and review channel selection
Create three pilot articles, publish each one to the right channels (Internal, Customer, Partner, Public), and confirm visibility in each surface (console, Help Center, agent search). Channel selection is the single biggest source of post-launch tickets.
One-way toggle that activates the KnowledgeArticleVersion object and the Lightning Knowledge UI. Cannot be reversed.
Per-user flag that gates the ability to read or author articles. Counted separately from the Service Cloud user license.
The master language for articles. Translations link back to this language. Cannot be changed after the first article publishes.
When enabled, each article supports translated versions tracked through PendingTranslation and Published states.
Shows excerpts with matched terms highlighted in search results, including in the Service Console article picker.
- Enabling Lightning Knowledge is irreversible in new orgs. Sandbox the decision and rehearse the article model before flipping the production switch.
- Data Category Visibility is profile-based, not user-based. A user inherits visibility from their profile only. Permission sets do not grant data category visibility.
- Channel selection at the article level overrides nothing on the sharing model. An article that is Public but the Knowledge object Org-Wide Default is Private still requires explicit sharing on the article to internal users.
- Search term history is purged on a rolling 90-day window. Build a Saved Report Type and a recurring snapshot if you want long-term content-gap data.
- Translations do not republish automatically. Set up a review queue or content goes stale silently in non-English markets.