Article Type
An Article Type in Salesforce Knowledge (Classic Knowledge) is a template that defines the structure and layout of a category of Knowledge articles.
Definition
An Article Type in Salesforce Knowledge (Classic Knowledge) is a template that defines the structure and layout of a category of Knowledge articles. Each Article Type has its own set of custom fields, page layouts, and workflow rules. For example, an organization might have Article Types for FAQs, How-To Guides, and Troubleshooting articles, each with different fields and layouts. In Lightning Knowledge, Article Types have been replaced by Record Types on a single Knowledge object.
In plain English
“In the old Classic Knowledge setup, an Article Type was like a template that defined what fields and layout a particular kind of article should use. FAQs had one template, how-to guides had another. In Lightning Knowledge, this has been replaced by Record Types on a single Knowledge object.”
Worked example
At Ridgeview Appliances' legacy Salesforce Classic Knowledge base, the knowledge manager defined four Article Types - FAQ, How-To, Troubleshooting, and Product-Spec. Each Article Type had its own custom fields (for example, Troubleshooting had Symptoms, Likely Cause, Resolution Steps; Product-Spec had Model Number, Dimensions, Warranty Terms) and its own publication workflow. When the org migrated to Lightning Knowledge, those four Article Types converted to four Record Types on a single Knowledge object - the separate Article Type objects no longer exist in Lightning Knowledge, but the concept of type-specific field layouts continued via Record Types.
Why Article Type matters
Article Type is a Classic Knowledge concept where each kind of article (FAQ, How-To, Troubleshooting, etc.) was modeled as a separate object with its own custom fields, page layouts, and workflow rules. Article Types provided structural flexibility because each type could have fields tailored to its purpose, but they also made reporting, cross-type search, and sharing significantly more complex because content was spread across multiple objects.
Lightning Knowledge replaces Article Types with Record Types on a single standard Knowledge object. This change simplifies the data model dramatically: all articles live in one place, share common metadata, and can be reported on uniformly. Different content structures (the old Article Types) are modeled as Record Types, which still let you have different page layouts and fields per type while benefiting from unified object-level features. Orgs migrating from Classic Knowledge to Lightning Knowledge go through an Article Type to Record Type conversion as part of the migration.
How organizations use Article Type
Migrated from Classic Knowledge with three Article Types (FAQ, How-To, Policy) to Lightning Knowledge with three Record Types on the Knowledge object. Reporting across all content became dramatically easier after the migration.
Still runs Classic Knowledge with several Article Types for historical reasons. They've documented the pain points and are planning a Lightning Knowledge migration for next year, which will consolidate everything into Record Types.
Used different Article Types in Classic Knowledge to give compliance articles a different workflow than standard support articles. In their Lightning Knowledge migration, they preserved this distinction using Record Types with separate approval processes.
Trust & references
Straight from the source - Salesforce's reference material on Article Type.
- Knowledge Article TypesSalesforce Help
- Create Article TypesSalesforce Help
Test your knowledge
Q1. What is an Article Type in Classic Knowledge?
Q2. What has replaced Article Types in Lightning Knowledge?
Q3. Why is the Lightning Knowledge model simpler than Classic?
Discussion
Loading discussion…