These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- DevOps Dashboard
- Features
- Operational knowledge
Operational knowledge
Review and publish service guidance with a clear owner.
OverviewPublished Knowledge Articles×
DevOps Dashboard · Operational knowledge
New
Published Knowledge Articles
Knowledge articles
| Title | Category | Published at | Owner | Service | Status | |
|---|---|---|---|---|---|---|
| Published ka-202 | CTG-102 | 16 Oct | SRV-1387 | Published | ||
| Published ka-898 | CTG-664 | 18 Oct | SRV-9852 | Published | ||
| Published ka-548 | CTG-205 | 11 Oct | SRV-7597 | Published | ||
| Published ka-363 | CTG-713 | 06 Oct | SRV-2688 | Published | ||
| Published ka-697 | CTG-569 | 05 Oct | SRV-3203 | Published |
6 of 6 records
Published ka-202Knowledge articles · KA-94718
PublishedCategoryCTG-102
Published at16 Oct
ServiceSRV-1387
What you can do
Keep guidance close to the service
A knowledge article has a title, category, body, owner, service, status and publication time. The service link helps a responder find guidance relevant to an incident or request. The owner gives the team a person to contact when instructions need correction. Article feedback records whether a reader found an article helpful, with a comment and submission time.
Consider a runbook for a recurring service issue. Its owner writes the operational steps and associates the article with that service. The review workflow routes a new article into Review. After the responsible team checks the instructions, a published article appears in the article library. A reviewer should read the steps against a real case before treating the guidance as ready for use.
How the work is organized
- Draft. The owner records the explanation and service context.
- Review. New guidance enters review before it is used as published material.
- Publish. The publication state and date show which guidance is available to the team.
What to agree during setup
Decide who owns each service’s knowledge and who checks new runbooks. Agree how to choose categories that help responders find an article at the moment they need it. Write down what a reviewer should confirm: the affected service, the procedure, and whether the content is safe for the intended audience. Make the publication time reflect the actual release of the article.
A review state means the article is being evaluated. It is not a substitute for the review itself. If an instruction changes after publication, the owner should revisit the article and its status. Archived articles remain useful for understanding earlier operational decisions while the published library focuses the current working guidance.
Check the handoff on an actual case
Create a draft article for an active service and follow its move into Review. Have a service desk manager check the procedure against a known incident or request. When it is ready, set the publication state and time and confirm it appears in Published Knowledge Articles. Open the article as an incident responder and check that the title and category make the right guidance discoverable.
After the rehearsal, submit article feedback for an unclear step. The owner should be able to read the comment and improve the text. Keep the article linked to its service so a future release or incident review can revisit the guidance that responders used.
What your team sees
- Published Knowledge Articles — Service guidance available to responders with owner and publication time.
- Open Incidents — Live cases where the guidance may apply.
Follow the work through
Use the knowledge review process to rehearse the move from draft to published 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.
- Incidents
- Incidents records for IT service and asset operations.
Who uses it
Permissions- Service Desk Manager
- , Incident Responder, Admin.
Set up DevOps Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.