CSA Guide

Knowledge Management in ServiceNow

Introduction

Knowledge Management turns your team's expertise into a reusable asset. A well-maintained Knowledge Base enables users to self-serve, reduces repeat incidents, and helps new agents resolve issues faster. ServiceNow's Knowledge module is deeply integrated with Incident Management and the Service Portal — but only if configured correctly.

Knowledge Base Structure

Knowledge Base
    └─ Category (e.g., "Hardware")
         └─ Sub-category (e.g., "Laptops")
              └─ Article (KB0000123)

You can have multiple Knowledge Bases for different audiences:

  • IT Knowledge Base: For service desk agents
  • Employee Self-Service KB: For end users via Service Portal
  • HR Knowledge Base: For HR-related policies and FAQs

Article Lifecycle

Draft → Review → Published → Retired
State Who can see it
Draft Author + Knowledge Managers
Review Reviewers
Published Configured audience
Retired No one (archived)

Publishing Workflow

For formal review before publishing:

  1. Author creates article in Draft
  2. Submits for review
  3. Knowledge Manager reviews and approves
  4. Article moves to Published state
  5. Notification sent to author

Enable workflow on the Knowledge Base record to activate this process.

Creating a Knowledge Article

Knowledge > Create New

Key fields:

  • Knowledge base: Which KB this belongs to
  • Category: Logical grouping
  • Short description: The article title (users search this)
  • Article body: Rich-text content
  • Valid to: Expiry date — article auto-retires when exceeded
  • Flagged for review: Marks article as needing attention

Article Body Best Practices

Structure articles for quick scanning:

  • Issue: One-line description of the problem
  • Environment: Affected systems/versions
  • Cause: Root cause if known
  • Resolution: Step-by-step fix
  • Workaround: Temporary fix while waiting for permanent resolution

Versioning

ServiceNow supports article versioning — when you update a published article, a new version is created and the old one is preserved:

KB0000123 v1.0 (Published 2024-01-15)
KB0000123 v2.0 (Published 2024-03-20) ← Current

Previous versions remain accessible in the version history for audit purposes.

User Criteria: Controlling Visibility

Control who can read articles using User Criteria (not ACLs):

User Criteria: IT Staff
  - Role: itil
  OR
  - Group: IT Department

Apply User Criteria at the Knowledge Base level (applies to all articles) or per-article.

Knowledge and Incident Integration

Attaching Articles to Incidents

Agents can attach knowledge articles to incidents from the form:

  • Related list: Knowledge Articles
  • Searching the KB inline while working a ticket

When a knowledge article resolves an incident, linking it builds usage data used to surface relevant articles in future.

Incident → Article: Creating from Resolution

When resolving a novel incident, agents can click Publish to Knowledge to create a draft article pre-populated with the incident's description and resolution notes. Review and publish to capture institutional knowledge automatically.

Knowledge Block

Knowledge Blocks are reusable content snippets that can be embedded in multiple articles — like a disclaimer or a standard procedure step. Update the block once; every article using it updates automatically.

Knowledge > Knowledge Blocks > New

Embed in an article: [[KB:SYS_ID_OF_BLOCK]]

Search and Relevance

ServiceNow's knowledge search uses full-text indexing. Improve search relevance:

  • Use keywords and tags on articles
  • Keep short descriptions accurate and descriptive (they are heavily weighted)
  • Avoid jargon that users wouldn't search for
  • Mark frequently helpful articles as Featured to boost ranking

Best Practices

  • Set a Valid to date on every article — stale articles erode trust
  • Assign a Knowledge Manager per Knowledge Base
  • Enable the feedback loop: link articles to resolved incidents
  • Create articles from incidents immediately after resolution (knowledge is freshest then)
  • Review flagged and expired articles monthly
  • Keep articles short — one resolution per article
  • Use categories that match how users think, not how IT is organized

Conclusion

A Knowledge Base is only valuable if it's current, relevant, and trusted. The discipline of creating articles from resolved incidents, setting expiry dates, and reviewing flagged content is what separates a knowledge base people use from one that collects dust. Build the habits, connect knowledge to your incident workflow, and the deflection rates will follow.

Keep reading this guide

Log in to access the full study guide and supercharge your preparation.