HR Knowledge Management and Employee Self-Service
Where content lives
HR answers live in knowledge bases structured with categories and articles. Each article has a workflow state (draft, review, published, retired), ownership, validity dates, and templated structure. The HR knowledge base is normally the default source for HR services and the Employee Center, and articles should be linked to the relevant HR service so employees move from question to action.
Who can see it
The single most tested concept: article visibility is governed by user criteria on the knowledge base and article (can read / cannot read, can contribute), not by HR criteria. User criteria can match user, group, role, department, company, location, or a script - but they read the user record, so HR-only attributes usually need a script or a synchronized field. HR criteria remain the tool for HR service and catalog visibility. Mixing them up is the classic distractor.
Self-service surface
Employee Center is the portal: topic pages, mega-menu, search across knowledge and services, and Virtual Agent topics for common questions. Case deflection is measured when employees resolve needs through search, knowledge, or virtual agent instead of opening a case - so article quality directly affects cost-to-serve metrics.
Traps
An article that exists, is active, and has a published workflow state can still be invisible because the knowledge base's can-read criteria exclude the employee. Conversely, published but expired (valid-to date passed) articles drop out of search. Articles in a different knowledge base do not appear unless that base is also readable.
Worked example
"Employees can't find the parental leave article in Employee Center." Check, in order: is the article published and not retired? Is the valid-to date in the future? Does the knowledge base can-read criterion include the employee's group/location? Is the article in a category the portal taxonomy exposes? Only then inspect search settings.