Knowledge Article
A Knowledge Article in Salesforce is the parent record in the Lightning Knowledge data model that holds metadata and version history for a single piece of help content used by service agents and customers.
Definition
A Knowledge Article in Salesforce is the parent record in the Lightning Knowledge data model that holds metadata and version history for a single piece of help content used by service agents and customers. Each Knowledge Article (KnowledgeArticle in the API) acts as a stable, permanent identifier, while the actual content — title, summary, body fields, attachments — lives on related Knowledge Article Version records (KnowledgeArticleVersion). This split lets a single article move through draft, published, and archived states without changing its URL or breaking inbound links from cases, communities, or external systems. Knowledge Articles can be authored in multiple languages (each translation is a separate version chain), categorized through Data Categories, restricted by visibility rules, and exposed across multiple channels: internal agent console, public help sites built with Experience Cloud, the Salesforce mobile app, and chat or bot deflection flows. Lightning Knowledge replaces the legacy Salesforce Classic Knowledge model, which used Article Types instead of Record Types and stored content in many parallel custom objects.
In plain English
“A Knowledge Article is one entry in your company's help library — like a single FAQ page or troubleshooting guide. The "article" is the permanent shell with a fixed URL, and the actual words inside it (the version) can be edited, translated, or replaced over time without breaking any links pointing to it. Service agents read articles to answer customer questions; customers read them on the help site to solve problems themselves.”
Worked example
A SaaS company's customer-success team writes a Knowledge Article titled "How to reset your two-factor authentication device." A senior agent drafts version 1 in English, sends it through an approval flow, and publishes it. Six months later a product change requires updating the steps — an agent edits the article, creating version 2 in Draft state while version 1 stays Published and visible. After review, version 2 is published and version 1 is archived automatically. The article's URL `/articles/reset-2fa` never changes, so support emails sent months ago still link correctly. A French translation chain is maintained in parallel for the EU customer base, with its own draft/publish lifecycle but the same article number.
Why Knowledge Article matters
The Lightning Knowledge data model has three layers: KnowledgeArticle (the stable parent), KnowledgeArticleVersion (the editable content, one row per version per language), and a per-record-type set of fields the admin defines (FAQ, How-To, Troubleshooting, etc.). SOQL queries against KnowledgeArticleVersion always need a PublishStatus filter (Draft, Online, or Archived) and a Language filter — omitting them returns all versions in all languages and quickly hits row limits. The article's ArticleNumber field is auto-incremented and human-readable; the Id changes per version while ArticleNumber stays constant.
Data Categories drive both visibility and search: an article can be tagged with one or more categories from a hierarchy (Products > Mobile App > iOS, for example), and a Data Category Visibility setting on each Profile or Permission Set controls who can read which branches. This makes Knowledge powerful for multi-product companies but introduces a subtle gotcha — adding a new top-level category requires explicit visibility grants on every existing profile, or no one will see the new content.
Lightning Knowledge supports article translation as a first-class feature. Each language is a parallel version chain under the same parent KnowledgeArticle, with its own draft/publish/archive lifecycle. Translations can be authored in-app, exported as XLIFF for a third-party translation service, then re-imported. Channel visibility (Internal App, Customer, Partner, Public Knowledge Base) is set per article version, so the same article can be drafted internally first, then exposed publicly once approved.
How organizations use Knowledge Article
Maintains a public help center with hundreds of Knowledge Articles covering account setup, billing, and troubleshooting. Articles are exposed through Experience Cloud and indexed by Google, deflecting an estimated 40% of would-be cases. Agents can attach articles to live chats with one click, with a CSAT survey on each suggesting which articles need rewriting.
Uses internal-only Knowledge Articles for clinical-policy reference (HIPAA, prescribing protocols, insurance pre-auth steps). Data Categories restrict cardiology articles to cardiology agents and pediatric articles to pediatric agents — the same visibility model that controls the agent app also controls the audit trail of who read what.
Maintains a Knowledge Article library translated into eight languages, with regional compliance teams owning each translation chain. The English master is published first; localized versions follow on a 5-day SLA. The shared article number lets headquarters track which markets have caught up after each policy change.
Trust & references
Straight from the source — Salesforce's reference material on Knowledge Article.
- Lightning Knowledge in Salesforce HelpSalesforce
Discussion
Loading discussion…