Starter · Part of Knowledge Management
In-app authoring with version history
Operations-managed authoring surface — list, new, edit, publish, archive, version history — backed by the same data model the client portal reads from. No engineering ticket to land a content change.
Internal authoring queue — every article across the tenant in one list with state, category, last-updated, and published-at columns. Editors filter by state across the full seven-state KCS lifecycle, search across title + summary + category, and jump straight into edit. Analytics and New article live one click away.
1 / 2
For the operator
Knowledge ops opens /knowledge each morning, picks up the drafts assigned to them, edits with a rich-text editor + category picker + audience picker, and publishes. The version history viewer surfaces the full edit chain; reverting to an earlier version is a one-click action that creates a new version row pointing at the old content (not a destructive rollback).
Business impact
Knowledge-platform adoption fails at the authoring layer more often than at the consumption layer — when authors won't use it, content goes stale. An accessible in-app authoring surface is the prerequisite for everything else the program delivers: search, analytics, cross-module links, compliance review.