Salesforce Lightning Knowledge New Features

Salesforce Knowledge has long been the go-to solution for organizations that need a robust knowledge base. It covered everything from internal support documentation to customer-facing self-service portals. Tightly integrated with Experience Cloud and Service Cloud, it enables teams to create, manage, and publish articles, organize content with data categories and topics, and deliver the right information to the right audience.

With the Spring ’17 Release, Salesforce introduced Lightning Knowledge — a fundamental reimagining of how Knowledge works within the platform. This was not just a facelift. The move to Lightning brought a redesigned data model, standard platform-aligned features, a modernized interface, and a roadmap built for faster, more flexible innovation. In short, it marked the end of the Classic-era limitations and the beginning of a more capable, scalable Knowledge experience.

In this article, you will learn:

• What Lightning Knowledge is and how it compares to Classic Knowledge
• The key goals behind the Lightning transition
• A full breakdown of new features and what each one means in practice
• How the simplified Salesforce knowledge data model benefits admins and reporting

What is Lightning Knowledge, and How it Differs from Classic Knowledge

Lightning Knowledge is Salesforce Knowledge rebuilt natively for the Lightning Experience. Rather than adapting a Classic-era product to a new interface, Salesforce rebuilt core knowledge functionality using standard Lightning platform patterns. The result is a Knowledge product that behaves like any other standard Salesforce object, making it far easier to configure, extend, and maintain.

Three differences stand out immediately:

• Data model: Classic Knowledge used multiple separate article type objects. Lightning Knowledge consolidates everything into a single Knowledge object, with record types handling differentiation.
• Interface: Classic Knowledge required the Salesforce Classic UI. Lightning Knowledge is built for the Lightning Experience, with a modern interface and unified navigation.
• Platform alignment: Many Classic Knowledge features were custom implementations. Lightning Knowledge uses standard Salesforce platform features like standard search, standard file handling, and standard permission sets, making it easier for admins familiar with Lightning to work with Knowledge.

The table below summarizes the key differences between Lightning Knowledge vs Classic Knowledge:

Key Goals of Lightning Knowledge

Salesforce built Lightning Knowledge around four strategic pillars. Understanding these helps explain why specific decisions were made in the design and release of the product.

Simplified Data Model

Knowledge in Salesforce Classic had multiple Article types. Lightning Knowledge has one single Article type, but you can create multiple record types. So, what’s the point of that? Well, you can use workflows across record types, you can report more easily across them, and you can share one field among different article types.

Platform Aligned Features

From all the areas in the Knowledge product, Salesforce has many custom ways of implementing features. In Lightning, Salesforce uses standard platform approaches. So, instead of Custom solutions in Salesforce Classic Knowledge features (like Data Model, Page Layout, Access and Permission, Search, and File Attachments, etc.), we will have Lightning Knowledge with a set of standard platform solutions.

Redesigned User Experience

The transition to Salesforce Knowledge Lightning Experience brings a cleaner, more consistent interface for both authors and consumers. The Unified Knowledge Tab replaces the separate Classic Knowledge and Article Management tabs, and the authoring experience is significantly improved.

Accelerated Innovation

By standardizing on the Lightning platform, Salesforce positioned Knowledge for faster feature development. New capabilities can be delivered through standard platform mechanisms rather than requiring custom Knowledge-specific builds.

New Features in Lightning Knowledge

The following features were introduced with the latest release. Each one addresses a specific limitation of Classic Knowledge or adds net-new capability with real practical value.

• Record Types: In Classic Knowledge, different article types were separate objects. Lightning Knowledge uses a single object with record types. The same mechanism is used across the Salesforce platform. This allows you to create different article structures (e.g., FAQs, How-To guides, Known Issues) while sharing fields, workflows, and reporting across all of them.
  
• List Views: Standard Salesforce list views are now available for Knowledge articles, replacing the limited views available in Classic. Authors and managers can filter, sort, and manage articles using the same list view framework used across every other Salesforce object, including inline editing where needed.
  
• Unified Knowledge Tab: Classic Knowledge required navigating between the Knowledge tab and the Article Management tab, depending on your task. Lightning Knowledge consolidates these into a single tab, reducing context-switching and making the article management experience more intuitive for agents and authors alike.
  
• Search in Global Search (with Filters): Lightning Knowledge articles are now indexed in Salesforce Global Search, which means agents and users can find articles alongside records, contacts, and cases, all from one search bar. Search filters allow users to narrow results by article type, data category, language, and more, significantly improving knowledge discoverability.
  
• Search Archived Articles: A notable gap in Classic Knowledge was the inability to search archived articles. Lightning Knowledge addresses this directly, allowing users to surface archived content when needed. It’s useful for compliance, historical reference, and recovery of previously published material.
  
• New Authoring Actions: Lightning Knowledge introduces updated authoring actions that align with the Lightning Experience action framework. Authors have access to a more streamlined publishing workflow, with actions that can be customized using standard Lightning configuration tools.
  
• New Files Component: File attachments in Classic Knowledge used a custom solution that did not integrate with Salesforce Files. Lightning Knowledge replaces this with a standard Files component, meaning attachments are now managed through the same framework as the rest of the platform. This simplifies storage management and improves consistency.
  
• New Rating Component: A redesigned rating component allows users to provide feedback on article quality. This is now built using standard Lightning component patterns, making it easier to customize or embed Knowledge in Experience Cloud pages.
  
• Update Article Votes: Authors and admins can now update vote data on articles, enabling better management of article quality signals over time. This is particularly useful when articles are updated and existing vote data may no longer accurately reflect the revised content.
  
• Page Layouts per Record Type: Classic Knowledge supported page layouts per article type. Lightning Knowledge extends this to page layouts per record type, using the standard Salesforce layout assignment mechanism. This makes it straightforward to present different fields and sections to different user profiles across different article categories.

Need help setting up or migrating to Lightning Knowledge?

AC Knowledge Management Enterprise is built specifically for teams that need a scalable, well-structured knowledge base in Salesforce. Our team can help you architect the right approach for your Experience Cloud or Service Cloud implementation. Get in touch to discuss your Knowledge management setup.

Simplified Data Model: Explained for Admins

If you have worked with Classic Knowledge, the data model change is the most significant architectural shift to understand. In Classic, each article type was a separate object, meaning you had separate fields, separate layouts, and separate reports for each type. As article types multiplied, so did the maintenance overhead.

Single Article Object Plus Record Types

Lightning Knowledge uses a single Knowledge__kav object for all articles. Record types are used to differentiate between article categories. The same pattern is used for Opportunities, Cases, Leads, and most other standard objects. This means:

• You create and manage fields once, on the shared object
• Fields can be shared across record types where relevant
• Workflows and automation apply across the entire Knowledge object
• You can assign page layouts per record type using the standard assignment interface

What Gets Easier: Reporting and Field Sharing

With a single object, reporting across all article types no longer requires cross-object report types or separate reports per article category. You build one report on the Knowledge object and filter by record type as needed. Field sharing, previously impossible across article types in Classic, is now a standard configuration step. If multiple article categories need a Resolution field, you create it once and include it on the relevant layouts.

Platform-Aligned Features: Why Admins Should Care

One of the most practical benefits of Lightning Knowledge is that it no longer requires administrators to learn a separate set of custom Knowledge-specific tools. The shift to standard platform patterns means your existing Lightning skills apply directly.

Permissions and access in Classic Knowledge used a custom tier system separate from standard Salesforce profiles and permission sets. Lightning Knowledge uses standard Salesforce permission sets and profiles, with Knowledge-specific permissions (like Read, Create, Edit, Publish, Archive) mapped to standard permission set configurations. If you already manage permissions through permission sets in your org, Knowledge fits into the same framework.

Page layouts follow the standard record type to layout assignment process — the same interface you use for Cases or Contacts. Search leverages the standard Global Search infrastructure with SOSL under the hood, meaning search behavior is consistent with the rest of the platform and can be tuned using standard search settings.

The result is a significantly lower maintenance burden for teams already running Lightning Experience orgs. There is no parallel configuration system to learn and maintain alongside the rest of your Salesforce setup.

Roadmap

Many features are already available in the Spring ’17 Release, like the single Knowledge Tab, Record Types, Global Search, Votes Update and List View. But most of the new features and improvements will be available after the Summer ’17 and Winter ’18 Releases.

Practical Checklist: Is Lightning Knowledge Right for Your Team?

Lightning Knowledge is particularly relevant for teams in these scenarios:

• Experience Cloud implementations with a customer-facing knowledge base or self-service portal
• Service Cloud orgs where agents rely on articles for case resolution
• Organizations with multiple article types that want unified reporting and shared fields
• Admins who want to manage Knowledge using standard platform tools rather than custom Knowledge-specific configuration

Before migrating or enabling Lightning Knowledge, review the following:

• Access and permissions: Map your existing Classic Knowledge user types and article type permissions to Lightning permission sets. Ensure your profiles and permission sets include the correct Knowledge object permissions.
• Article structure: Audit your existing article types and plan how they map to record types in Lightning. Identify which fields can be shared and which are specific to individual record types.
• Search configuration: Review your data categories and topic assignments. Verify that articles will surface correctly in Global Search after migration.
• Archived articles: Determine which archived articles should remain searchable and ensure they are accounted for in your migration plan.
• Files and attachments: Identify any articles with file attachments managed through the Classic custom solution and plan for their migration to the standard Files component.

Summary

Lightning Knowledge represents a significant and well-considered evolution of Salesforce Knowledge. By moving to a single article object, standard platform features, and the Lightning Experience, Salesforce has made Knowledge substantially easier to configure, maintain, and extend, while also expanding what is possible in terms of search, reporting, and user experience.

For teams running Experience Cloud portals, Service Cloud contact centers, or any Salesforce org where a well-structured knowledge base matters, Lightning Knowledge is the right foundation. The simplified data model reduces admin overhead, platform-aligned features reduce the learning curve, and the expanding feature set supports increasingly sophisticated knowledge management requirements.

Evaluating How to Best Structure Your Knowledge Implementation?

We recommend working with a trusted Salesforce implementation partner. The Advanced Communities team has years of experience building knowledge bases and full self-service portals, knowledge hubs, support portals, and other types of comprehensive sites with well-structured Knowledge foundations. Contact us to discuss your needs and find the best solution for you.