Administration · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
Knowledge lifecycle
Publishing workflow, versioning, feedback and the governance that keeps articles trustworthy.
Quick answer
Publishing workflow, versioning, feedback and the governance that keeps articles trustworthy.
Key takeaways
- Versioning lets you edit without unpublishing
- User criteria control read and contribute separately
- Every knowledge base needs an owner and a review cycle
- Feedback and search analytics show which articles fail
Lifecycle
Articles move through draft, review, published and retired, controlled by a knowledge workflow on the knowledge base. Versioning keeps the published article live while a new version is edited, which is the feature most teams forget exists.
Access and ownership
User criteria control who can read and who can contribute per knowledge base. Every base needs an owner and a review cycle, otherwise articles age silently and trust collapses.
Feedback loop
Article quality is measurable.
- Track useful votes, views and search hits with no click
- Route flagged articles to the owner with a due date
- Retire rather than delete so links do not break
- Create articles from incidents while the detail is fresh, not in a quarterly push
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What lets you edit a published article without taking it offline?
Frequently asked questions
How many knowledge bases should we have?
One per audience with genuinely different access rules. More bases means more governance overhead and worse search relevance.
Who should approve articles?
A subject matter expert for accuracy plus, where relevant, a compliance reviewer. Approval by committee stalls publishing.