kb_category Table — ServiceNow Reference

Table Reference/kb_category

The `kb_category` table stores categories within knowledge bases, forming a hierarchical tree structure used to organize knowledge articles. Owned by the Knowledge Management module, this table is critical for content taxonomy and navigation. The key thing developers must know is that categories are scoped to specific knowledge bases and form parent-child relationships through the `parent` field.

What This Table Is

The kb_category table stores knowledge base categories that create the hierarchical taxonomy for organizing knowledge articles. Each record represents a category node that can have parent and child relationships, enabling the tree structure that users navigate when browsing knowledge articles by topic.

This table is owned by the Knowledge Management module and supports the end-to-end content organization process from knowledge base creation through article publication and user consumption. Categories serve as both organizational containers and navigation aids, allowing knowledge authors to classify content and end users to discover relevant articles through browsing rather than search.

The table does not extend any parent table and is not commonly extended by child tables. Instead, it forms relationships through the self-referencing parent field and connects to knowledge articles through the kb_knowledge table's kb_category reference field.

Record volumes in this table are typically moderate, even in large enterprises. Most organizations maintain 50-500 categories across all knowledge bases, though complex implementations may reach 1,000+ categories. The hierarchical nature means query performance depends heavily on tree depth and the efficiency of parent-child traversal operations.

When You'll Script Against This Table

Developers typically interact with kb_category in Business Rules for category validation, Script Includes for building navigation trees, UI Actions for bulk category operations, and Client Scripts for dynamic category filtering. Background scripts are common for category maintenance and data migration tasks.

Access to this table requires the knowledge_admin role for full CRUD operations, while knowledge_manager provides limited access within specific knowledge bases. The table respects knowledge base scoping rules, so users only see categories for knowledge bases they have access to.

Building hierarchical navigation menus for knowledge portals
Validating category assignments to prevent orphaned articles
Calculating article counts per category for display purposes
Migrating category structures between knowledge bases
Enforcing category depth limits to prevent overly complex hierarchies
Generating category-based reporting for content analytics
Creating category templates for consistent knowledge base setup

Table Gotchas

⚠️

The `parent` field creates self-referencing relationships that can form infinite loops. Always validate parent assignments to prevent circular references that break navigation trees.

The kb_knowledge_base reference field enforces scoping but can be null for global categories, leading to unexpected query results

⚠️

Deleting categories with child categories or associated articles requires cascade handling. The platform doesn't automatically prevent deletion of categories that would orphan content.

The order field only controls sibling ordering within the same parent level, not global category ordering
Category names are not unique across knowledge bases, so queries must include knowledge base filtering to avoid duplicates

⚠️

Tree traversal queries can be expensive with deep hierarchies. Consider caching category trees or using path-based approaches for frequently accessed navigation structures.

The active field affects visibility but inactive parent categories can still have active children, creating broken navigation paths

Free Newsletter

Enjoying this? Get one deep-dive per week.

Join 1,000+ ServiceNow pros — scripts, GlideRecord patterns, Flow Designer techniques, and career moves. Free.

The kb_knowledge table is the primary related table, as each knowledge article references a category through its kb_category field. The kb_knowledge_base table defines the knowledge base scope that contains categories and determines access permissions.

The sys_user_group and sys_user tables connect through knowledge base permissions and category management rights. Developers commonly query these together when building category-filtered article lists, validating user access to specific category trees, or generating navigation menus that respect user permissions.

The self-referencing relationship through the parent field means developers frequently perform recursive queries within the same table to build complete category hierarchies or validate tree structures.

Chrome Extension

Sourdough: ServiceNow Monitoring and Analytics

A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.

Instance HealthGraphs & ChartsAPI HealthDeveloper ToolsQuick SearchInstance Switcher

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview

Tasks

CMDB

API

Metrics

Monitor

Internals

Instance:sourdoughdev·Version:Yokohama

Instance StateONLINE

System StatusFully Operational

Session Timeout90 minutes

Logged-In Sessions2 (20 active)

Build Nameyokohama-12-18-2024_p1

IP Address10.159.128.43

Instance HealthHealth Score: 90%

🔥 5dSourdough (Chrome Plugin)Dark Mode

Key Fields

Column	Type	Label	Notes
label	string	Label	The display name of the category shown to users. Not unique across knowledge bases, so multiple categories can share the same label.
kb_knowledge_base	reference	Knowledge Base	References the kb_knowledge_base table to scope this category to a specific knowledge base. Can be null for global categories accessible across all knowledge bases.
parent	reference	Parent Category	Self-referencing field to kb_category for hierarchical structure. Null indicates a root-level category. Requires circular reference validation to prevent infinite loops.
active	boolean	Active	Controls category visibility in user interfaces. Inactive categories remain in the database but are hidden from navigation and selection lists.
order	integer	Order	Controls display order among sibling categories at the same hierarchy level. Lower numbers appear first. Does not affect ordering across different parent levels.
description	string	Description	Longer text describing the category's purpose or scope. Often displayed as tooltips or help text in category selection interfaces.
image	string	Image	Stores the sys_id of an attachment record for category icons or images. Used in portal interfaces for visual category representation.
disable_commenting	boolean	Disable Commenting	When true, prevents user comments on knowledge articles within this category. Inherited by child categories unless explicitly overridden.
disable_rating	boolean	Disable Rating	When true, prevents user ratings on knowledge articles within this category. Affects article feedback mechanisms and analytics.
full_category	string	Full Category	Calculated field showing the complete category path from root to current category. Automatically maintained by the platform for display and search purposes.
topic	string	Topic	Optional topic classification for the category. Used for additional grouping and filtering beyond the hierarchical structure.
source	choice	Source	Indicates how the category was created (manual, imported, migrated). Important for data governance and migration tracking.
workflow_state	choice	Workflow State	Tracks category approval status in workflows. Categories may require approval before becoming available for article assignment.
manager	reference	Manager	References sys_user table for the user responsible for managing this category. Used for ownership tracking and approval routing.
url	string	URL	External URL associated with the category. May link to additional resources or redirect users to related content outside the knowledge base.

Common Queries

Get all active categories in a specific knowledge base

// Most basic query - filter by knowledge base and active status
var gr = new GlideRecord('kb_category');
gr.addQuery('kb_knowledge_base', 'your_kb_sys_id');
gr.addQuery('active', true);
gr.orderBy('order');
gr.orderBy('label');
gr.query();
while (gr.next()) {
    // Process each active category
    gs.info('Category: ' + gr.getDisplayValue('label'));
}

Find root categories with active workflow state for a specific manager

// Query combining null parent check with reference and choice fields
var gr = new GlideRecord('kb_category');
gr.addNullQuery('parent');  // Root level categories only
gr.addQuery('workflow_state', 'approved');
gr.addQuery('manager', gs.getUserID());  // Current user as manager
gr.addQuery('active', true);
gr.orderBy('order');
gr.query();
while (gr.next()) {
    gs.info('Root category managed by you: ' + gr.getDisplayValue());
}

Get all child categories of a parent category for navigation tree building

// Real-world scenario - building hierarchical navigation
var parentCategoryId = 'parent_category_sys_id';
var gr = new GlideRecord('kb_category');
gr.addQuery('parent', parentCategoryId);
gr.addQuery('active', true);
gr.orderBy('order');
gr.query();

var children = [];
while (gr.next()) {
    children.push({
        sys_id: gr.getValue('sys_id'),
        label: gr.getDisplayValue('label'),
        hasChildren: this._hasChildCategories(gr.getValue('sys_id'))
    });
}
return children;

Count articles per category using GlideAggregate

// Aggregate query to count knowledge articles by category
var agg = new GlideAggregate('kb_knowledge');
agg.addQuery('workflow_state', 'published');
agg.addNotNullQuery('kb_category');
agg.groupBy('kb_category');
agg.addAggregate('COUNT');
agg.query();

while (agg.next()) {
    var categoryId = agg.getValue('kb_category');
    var articleCount = agg.getAggregate('COUNT');
    gs.info('Category ' + categoryId + ' has ' + articleCount + ' published articles');
}

Wrong vs right way to validate parent-child relationships

// WRONG - can create circular references
// var gr = new GlideRecord('kb_category');
// gr.setValue('parent', someParentId);
// gr.update();

// RIGHT - validate no circular reference before setting parent
var categoryId = current.getValue('sys_id');
var newParentId = current.getValue('parent');
if (newParentId && this._wouldCreateCircularReference(categoryId, newParentId)) {
    gs.addErrorMessage('Cannot set parent - would create circular reference');
    current.setAbortAction(true);
}

// Helper method checks if parent chain leads back to original category

Test Your Knowledge

Quick 3-question quiz — see how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue

kb_category