Knowledge lifecycle
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
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What lets you edit a published article without taking it offline?
- A. Cloning
- B. Versioning
- C. Retiring
- D. Flagging
Show answer
B. Versioning
A new version is edited while the current version stays published.
What controls who can contribute to a knowledge base?
- A. ACL only
- B. User criteria
- C. Assignment rules
- D. Data policies
Show answer
B. User criteria
User criteria define read and contribute access per base.