Article-Type Layouts no longer exist in Lightning Knowledge. The live equivalent is a standard page layout assigned per record type and profile on the Knowledge object. Here is how an admin sets that up today.
- Create or open the record type
In Setup, go to the Knowledge object and open Record Types. Create one record type per kind of article, for example FAQ or Procedure. This is the Lightning replacement for a Classic article type.
- Build the page layout
Under the Knowledge object Page Layouts, create or edit a layout. Drag in the fields and sections each article kind needs, and place authoring actions in the Salesforce Mobile and Lightning Experience Actions section.
- Add the Publication Status field
Put the Publication Status field on the standard page layout, not on a compact layout, so authors can use inline edit on the article record.
- Assign the layout per record type and profile
Open the Page Layout Assignment screen and map each profile and record type combination to the right layout, so each audience sees the correct fields.
The Lightning container that replaces a Classic article type and owns its layout assignment.
The standard layout that decides which fields, sections, and actions appear on the article.
Must be on the standard layout, not a compact layout, to enable inline edit for Knowledge.
The per profile and record type mapping that controls which layout each author sees.
- Permissions do not come from the layout. Lightning uses profiles and permission sets, replacing the Classic article actions model, so grant access separately.
- Fields that Classic hard-coded onto the article screen are not added for you. Place them on the layout by hand after migration.
- Leaving Publication Status off the standard layout silently breaks inline edit, which is easy to miss until an author reports it.