Question

Difficulty: HardSalesforce Knowledge Setup and Management

A system administrator at a global financial advisory firm is configuring Salesforce Knowledge for internal wealth managers. The administrator assigned Knowledge User feature licenses to all wealth managers, created a Data Category Group called "Investment_Products", published several internal articles, and mapped them to categories within this group. Wealth managers have Read, Create, and Edit access on the Knowledge object, and object-level Organization-Wide Defaults (OWD) are set to Public Read-Only. However, wealth managers report that searching for published articles yields zero results, whereas system administrators can view and read all articles without issue. Which omitted configuration step is causing wealth managers to be unable to view these published Knowledge articles?

  1. Data Category visibility for the "Investment_Products" category group was not assigned to the wealth managers' roles, profiles, or permission sets.Answer
  2. B
    Wealth managers were not assigned a custom permission set granting the "Manage Knowledge" administrative permission.
  3. C
    The "Investment_Products" record type was not assigned to the active Knowledge publication channel picklist.
  4. D
    Organization-Wide Default (OWD) sharing settings on the Knowledge object override Data Category visibility assignments, forcing Private access.

Answer

Data Category visibility for the "Investment_Products" category group was not assigned to the wealth managers' roles, profiles, or permission sets.
In Salesforce Knowledge, article visibility is controlled by Data Category visibility rules assigned through User Roles, Profiles, or Permission Sets. If an administrator creates a Data Category Group and assigns articles to it without granting category visibility to the target user group, those users cannot see or search for those articles regardless of their object-level permissions.

Step-by-Step Solution

1
Evaluate Object and User License Access
Wealth managers have Knowledge User feature licenses and Read/Create/Edit object permissions, confirming baseline object and feature access is intact.
Knowledge accessibility requires feature licensing and CRUD permissions before evaluating article filtering.
2
Evaluate Data Category Visibility Architecture
In Salesforce Knowledge, visibility of categorized articles is driven by Data Category Group visibility settings assigned at the Role, Profile, or Permission Set level.
Even with Public Read-Only OWD and full object access, users cannot see articles if they lack Data Category visibility for the category group.
3
Identify Missing Administrative Configuration
The administrator must grant visibility (e.g., All Categories, Custom, or Parent-Child visibility) for the "Investment_Products" category group to the target users' roles, profiles, or permission sets.
Granting Data Category visibility exposes the published articles associated with those category paths.

Key Concept

Salesforce Knowledge Data Category Visibility
Estimated Time:2m 0s
Rate this question