Knowledge Management

Knowledge Base Structure

ServiceNow organizes knowledge using a three-level hierarchy. Understanding this hierarchy — and the underlying tables that support it — is fundamental for both the exam and day-to-day administration.

The Three-Level Hierarchy

Key Tables — Exam Reference

Multiple Knowledge Bases Per Instance

A single ServiceNow instance commonly runs several Knowledge Bases simultaneously, each scoped to a specific audience or domain:

Knowledge Article Lifecycle

Every knowledge article progresses through a defined set of states. Understanding these states — particularly which state makes an article visible to end users — is one of the most tested areas on the CSA exam.

Article States

Lifecycle Flow

Article Number and Identification

• Each article receives an auto-generated article number with the KB prefix (e.g., KB0001234)
• The number is stored in the number field on kb_knowledge
• Article numbers are unique across the instance regardless of which KB the article belongs to

Versioning and Validity

Knowledge Roles

ServiceNow uses a tiered role model for Knowledge Management. Each role grants a specific level of access across the Knowledge Base hierarchy. These roles are frequently tested on the CSA exam.

Role Hierarchy

Role Comparison Table

KB Owner Field

Each Knowledge Base record has an Owner field and a KB Managers field. Users listed in these fields automatically receive knowledge_manager-level control over that specific KB, even without the global knowledge_manager role.

Access Control for Knowledge

Knowledge access control works at three layers: Knowledge Base level, Category level, and Article level. These layers work together to create fine-grained control over who can read and contribute to knowledge content.

Layer 1 — Knowledge Base Level

The "Accessible by" field on the Knowledge Base record is the primary access gate. It determines the audience for all articles within that KB.

Layer 2 — Category Level

Individual categories within a KB can apply additional restrictions. A category can be more restrictive than its parent KB — for example, an IT Knowledge Base may be accessible to all logged-in users, but a "Security Incidents" category within it can be restricted to the security team only.

Layer 3 — Article Level (User Criteria)

Individual articles support the most granular access control through User Criteria. User Criteria are reusable access rules that can be applied to both reading and contributing.

User Criteria Records

User Criteria are records in the user_criteria table that define a named set of users based on:

• Specific users (by reference to sys_user)
• Groups — all members of a specified group
• Roles — all users holding a specified role
• Companies — for multi-company/tenant scenarios
• Departments — organizational unit-based access

Knowledge Workflows

Knowledge workflows govern how articles move through their lifecycle states. ServiceNow provides default workflows and allows customization per Knowledge Base.

Default Workflows

Workflow Configuration Per KB

• Navigate to the Knowledge Base record and look for the Workflow field
• Select the approval workflow to use — defaults to the system default workflow
• Different KBs can use entirely different approval chains
• The HR Knowledge Base might require an HR director approval, while IT KB goes to the IT manager

Workflow Bypass — knowledge_admin

Approval Flow Detail

Contributor creates article (Draft)
    ↓
Contributor clicks "Submit for Review"
    ↓ [Workflow triggers]
Article state → Review
    ↓
Approval task sent to KB Manager
    ↓
KB Manager reviews content
    ├── Approved → Article state → Published (visible to users)
    └── Rejected → Article state → Draft + comments returned to author

Knowledge in Service Portal

The Service Portal is the primary self-service interface where end users interact with Knowledge Management. ServiceNow provides several out-of-box widgets and integration points for surfacing knowledge content.

Knowledge Widgets in Service Portal

How Related Articles Surface in Incidents

When an agent is working an incident, ServiceNow can automatically suggest relevant knowledge articles. This integration requires:

• A Knowledge widget or Related Knowledge section configured on the incident form
• Published articles in a KB that the agent has read access to
• Text in the incident's short description or work notes to drive the search query
• The agent can then review suggestions and attach a relevant article with one click

Service Portal Navigation Path

Service Portal Home
  └── Knowledge Base (top nav or search bar)
        └── Select Knowledge Base (IT, HR, etc.)
              └── Browse Categories
                    └── Browse Sub-categories (if nested)
                          └── Open Article → Rate / Flag / Attach to Record

Feedback and Flagging

ServiceNow Knowledge Management includes a feedback loop that allows users to rate articles and flag content for review. This data helps knowledge managers identify high-quality articles and those needing improvement.

Article Rating System

The kb_feedback Table

All feedback interactions — ratings, comments, and flags — are stored in the kb_feedback table. Key fields include:

Using Feedback Data

• Knowledge managers can run reports on kb_feedback to identify low-rated articles needing revision
• Articles with many "Not Useful" responses are candidates for rewriting or retirement
• Highly rated articles are surfaced higher in search results (relevance boost)
• Flagged articles appear in the knowledge manager's dashboard for immediate attention
• Feedback data can be used in dashboards and performance analytics to measure KB health

Key Exam Facts & Common Traps

This section consolidates the most frequently tested Knowledge Management facts and the most common wrong-answer traps on the CSA exam. Review this section before your exam.

Quick-Reference: All Key Facts