Knowledge Base vs Article vs Knowledge Block.

Collection, content and reusable fragment

Knowledge Base: governance for a collection

A knowledge base groups related articles and establishes who owns, manages, reads and contributes to the collection. Examples include IT Support, Human Resources and Customer Product Help. It is more than a folder: its configuration influences the authoring and consumption model for every article it contains.

• Can Read / Cannot Read user criteria determine who can view articles in the base.
• Can Contribute / Cannot Contribute determine who can create, modify and retire articles in the base.
• Owners and managers administer the base and its governance.
• Categories organize content inside a base but do not replace access controls.
• Features such as knowledge blocks are enabled for each applicable base.

Security rule: if a user matches both an allow and a deny user criterion at the same knowledge level, ServiceNow denies access. Validate the result with User Criteria Diagnostics rather than assuming membership grants visibility.

Knowledge Article: the publishable answer

An article is the content record readers search for and open. Its fields commonly include a number, short description, body, knowledge base, category, author, workflow state, validity dates and reader criteria. Article templates can provide consistent structures for FAQs, how-to instructions, policies or known errors.

Publishing workflows vary with configuration and versioning, but the central lifecycle is consistent: draft content is reviewed, published for permitted readers and eventually revised or retired. A category helps users browse; it does not make an unreadable article visible.

Knowledge Block: reusable and audience-aware content

Knowledge blocks are reusable content components that contributors insert into one or more articles. ServiceNow supports text and images in blocks. They are useful when the same approved instruction, contact detail or regional paragraph must appear consistently across multiple articles.

A knowledge administrator must activate the knowledge-block plugin and a knowledge administrator or manager must enable blocks for the applicable base. Contributors can then insert blocks into article HTML fields. A reader who can open the article but cannot read one embedded block still sees the article without that block content.

Trace access from base to article to block

1. Start at the base: does the user meet its read criteria and avoid its Cannot Read criteria?
2. Check the article: does article-level reader configuration allow the user, and is the article in a readable state?
3. Check each block: Can Read and Cannot Read user criteria can further tailor embedded block content.
4. Separate contribution: Can Contribute and Cannot Contribute apply at the base level to creating, modifying and retiring articles.
5. Test the person, not an admin: impersonate a representative reader and use diagnostics because administrators and knowledge owners can have elevated access.

ServiceNow documents that a matching Cannot Read criterion wins over Can Read at the same level. It also notes that users who meet a base Can Contribute criterion can read block content in that base. Design criteria intentionally and test every intended audience.

Worked scenario: a password-reset knowledge program

The service desk needs searchable instructions for employees and a deeper diagnostic procedure for support staff.

1. Create an IT Support Knowledge Base and assign the correct owners, managers, reader and contributor criteria.
2. Create a Knowledge Article named “Reset your corporate password” with public employee steps.
3. Create a support-only Knowledge Block containing identity-verification and escalation details; restrict it to the service-desk audience.
4. Insert the block into the same article so agents receive additional instructions without maintaining a duplicate article.
5. Place the article in a Passwords category for navigation, then test employee and agent personas separately.

This design minimizes duplicated content while keeping specialized instructions controlled. Creating two nearly identical articles would increase drift and make future corrections harder.

Troubleshoot a missing or incomplete article

1. Confirm lifecycle: published state, active/version status, valid-from and valid-to dates.
2. Test base access: Can Read, Cannot Read, roles, ownership and relevant platform properties.
3. Test article access: article user criteria and any supported role restrictions.
4. Inspect the block: if only part of the article is absent, verify block user criteria and that blocks are enabled for the base.
5. Check context: language, domain, portal, channel, selected knowledge bases and article version.
6. Check discovery: category placement, search source, indexing and whether a recent publication has reached the index.
7. Use diagnostics: run User Criteria Diagnostics for the affected user and impersonate a safe test persona.

Common mistake: testing as admin can hide a reader-access problem. Reproduce the issue with the affected audience and record which criterion grants or denies each level.

ServiceNow CSA practice checks

Frequently asked questions

Official ServiceNow references

Validate configuration against current ServiceNow documentation for knowledge-base and article access, knowledge blocks, adding blocks to an article and block user criteria. Features and defaults vary by release, installed applications and instance configuration.