The knowledge base is designed to protect your work. It automatically saves changes and keeps a history of published versions so you can edit confidently.
How auto-save works
Auto-save ensures your changes are never lost while editing.
Changes are saved automatically as you type.
There is no manual save button for regular edits.
If you leave the page and return, your draft changes remain.
Auto-save applies to draft changes only. Published content is not affected until you publish again.
When an article is first created
When you create a new article:
It starts in a not saved state.
It is not visible to other technicians yet.
Once you click save as draft:
The article becomes visible to other technicians on your account.
The draft is now collaborative.
Auto-save continues to protect ongoing edits.
Understanding draft versions
A draft version represents the latest unpublished changes.
Drafts are saved automatically.
Drafts do not affect the live version.
Multiple technicians can edit the same draft.
If needed, you can:
Continue editing the draft
Discard the draft
Publish the draft
Understanding published versions
When you click publish:
A new published version is created.
The article becomes live.
The previous published version is stored in version history.
The current active version is marked with a live tag.
Viewing version history
Each article contains a version history tab in the right panel.
From version history, you can:
See all previously published versions
Identify the version marked as live
Review the timeline of updates
Restore older versions if needed
Version history protects against accidental overwrites.
Restoring a previous version
If content needs to be reverted:
Open the article.
Go to the version history tab.
Select the version you want to restore.
Click restore.
The restored version becomes the new live version.
No versions are permanently lost during this process.
Discarding draft changes
If you want to remove all unpublished edits:
Click discard draft.
Confirm when prompted.
This action:
Removes all draft changes
Reverts the article draft to the last published version
Discarding cannot be undone.
Best practices
Review changes before publishing.
Use version history instead of rewriting content manually.
Discard drafts only when you are sure changes are not needed.
Auto-save and version history work together to ensure your knowledge stays protected, organized, and recoverable.