Every article in the knowledge base keeps track of its changes. This helps you edit freely while still protecting stable, published content.
Draft versions explained
When an article is edited, it exists as a draft until published.
Any edits you make are saved automatically to the draft.
Drafts capture all ongoing changes.
Drafts are not considered final and can be updated at any time.
Draft content is not visible as the live version outside the DeskDay KB until it is published.
Saving a draft
Click save as draft to keep your changes without publishing them.
This is useful when the article is not ready to go live.
Discarding a draft
Click the X button at the top right.
A confirmation modal will appear.
Click discard to remove all draft changes.
This helps avoid saving unfinished or unwanted edits.
Draft versions are useful when:
You are still working on content
You want to review changes before sharing
Multiple people are collaborating on updates
Published versions explained
When an article is published, it becomes an official version.
Published articles are visible and usable as intended.
Each time you publish, a new published version is created.
Older published versions are not deleted. They are stored safely. The current published version is marked with a “live” tag, making it easy to identify.
Viewing version history
For every article, you can:
See a list of all published versions
Check when each version was published
Identify the latest active version
If any technician makes changes, a draft version is created and made available for collaborative editing.
This gives you a clear timeline of how the article has evolved.
Restoring an older version
If something goes wrong or content needs to be rolled back:
Open the article.
Open the version history.
Select a previously published version.
Restore that version.
The restored version becomes the current version.
What happens to drafts after publishing
New edits after publishing are saved as a new draft.
You can continue editing without affecting the published version until you publish again.
This allows safe experimentation without risk.
Best practices for versions
Publish only when content is reviewed and ready.
Use drafts for ongoing changes.
Restore older versions if incorrect updates are published.
Avoid overwriting published content without checking history.