1. IT Service Management
  2. Features
  3. Knowledge
Feature · Knowledge

Knowledge

Review service guidance and maintain a visible publication state.

OverviewPublished Knowledge Articles
IT Service Management · Knowledge

Published Knowledge Articles

Knowledge articles

New
IdTitleCategoryStatusPublished atOwner
IDD-210Published ka-890CTG-249Published15 Oct
IDD-128Published ka-822CTG-585Published03 Oct
IDD-790Published ka-156CTG-311Published25 Oct
IDD-792Published ka-908CTG-486Published14 Oct
IDD-669Published ka-395CTG-857Published25 Oct
6 of 6 records
IDD-210Knowledge articles · KA-20767
Published
TitlePublished ka-890
CategoryCTG-249
Published at15 Oct
ServiceSRV-2138
Example screen with sample data

What you can do

Give guidance an owner

A knowledge article has a title, category, body, service, owner, status and publication date. This lets the team keep draft guidance apart from material marked published or archived. A service desk agent can look for published guidance while answering a recurring question. The owner remains responsible for whether the content still fits the service and its current operation.

The knowledge workflow routes a created record into review. A person still needs to decide whether the article is ready and maintain its status. Feedback records can capture whether a reader found an article helpful, a comment and submission time. Those signals help the Knowledge Owner decide which guidance deserves another look.

How the work is organized

  • Draft. Write a precise article for a named service and category, with an accountable owner.
  • Review. Check the guidance before moving it through the review and publication states.
  • Maintain. Use article feedback and service changes to decide when a published article needs revision or archiving.

What to agree during setup

Decide who may move an article to published and who checks guidance after a service change. A published article should answer a real operational question with steps the desk can apply. Agree whether the body is meant for internal responders or for a separate customer channel before distributing it. The article record gives the owner a place to maintain the source content; any external publication channel is a connection to configure.

Keep categories useful to the people searching the library. A broad category may hide a specific restoration procedure, while a category defined around a single case may not help the next responder. Review the service link and owner as part of the article review.

Check the handoff on an actual case

After several incidents on the same service, the Knowledge Owner writes a recovery article. The record includes its title, category, instructions, owner and service. The article enters review. Another person checks the steps against the current service before the status is moved to published and a publication date is entered. The Service Desk Agent then uses the published library to find it during the next similar incident.

A reader marks the article unhelpful and explains where a step is stale. The owner reviews the comment and revises the body or archives the article if the procedure no longer applies. The article’s status should match what the desk is allowed to use for new work.

What your team sees

  • Published Knowledge Articles — Guidance marked published for desk use.
  • Article library — The broader article register for editorial review.

Follow the work through

Follow knowledge review from draft to publication. Use incident response to see where responders need current guidance.

What it keeps track of

Data model
Knowledge articles
Knowledge Articles records for IT service and asset operations.
Article feedback
Article Feedback records for IT service and asset operations.
Services
Services records for IT service and asset operations.
People
People records for IT service and asset operations.

Who uses it

Permissions
Knowledge Owner
, Service Desk Agent, Incident Responder.

Set up IT Service Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started