Configuring the options that the Enhanced Knowledge Settings docs referred to means configuring the standard Knowledge Settings page after enabling Lightning Knowledge. The workflow is the same as configuring Lightning Knowledge in general.
- Confirm Lightning Knowledge is enabled
Setup, Knowledge Settings, Enable Lightning Knowledge. The Enhanced options become available after this toggle.
- Configure per-record-type page layouts
Setup, Object Manager, Knowledge, Record Types. For each record type (FAQ, How-To, Known Issue), define a page layout with the appropriate field set and Article Actions.
- Set default channel checkboxes per record type
On each record type's page layout, configure the default values for IsVisibleInApp, IsVisibleInCsp, IsVisibleInPrm, IsVisibleInPkb. Authors can override per article.
- Configure rich text body fields per record type
Add a rich text Body field to each record type's page layout. The field is per-record-type, so FAQ might have a Question and Answer rich text field, How-To might have Problem and Steps.
- Enable Multiple Languages if multilingual
Knowledge Settings, Enable Multiple Languages. Add the secondary languages. Each adds a translation lifecycle to articles.
- Configure Article Voting if needed
Knowledge Settings, Enable Article Voting. Configure public voting and internal voting separately.
- Set up Synonym Groups
Setup, Search, Synonym Groups. Build the synonym sets that improve search recall for internal terminology.
- Document the configuration for editors
Publish a Knowledge Article or training note explaining the per-record-type configuration so authors can use it correctly.
Different layouts per article variant, with distinct field sets, Article Actions, and rich text fields.
Defaults for IsVisibleInApp, IsVisibleInCsp, IsVisibleInPrm, IsVisibleInPkb configured at the record type level.
Article body fields are rich text per record type, not one global body.
Translation workflow unlocked through the Knowledge Settings page after Lightning Knowledge is enabled.
The Lightning search ranking model with view-count and attach-rate weighting.
Per-record-type voting configuration for helpful/not-helpful feedback.
- Enhanced Knowledge Settings is mostly a documentation term, not a separate Setup page. The configuration lives in Knowledge Settings and the per-record-type page layouts.
- Per-record-type page layouts require deliberate planning. Cap record types at 4 to 5; more usually means a single record type with conditional fields would have been simpler.
- Channel checkbox defaults at the record type level are overridable per article. Authors who forget to check the right channel get unpublished or invisible articles.
- Multilingual articles do not auto-translate when the master republishes. Translations get marked outdated; translators must update them manually.
- Synonym Groups apply globally to the org. A synonym that helps the support team may confuse the sales team. Build synonyms carefully.