π How the Document Register Works
π
Document IDs
Each document gets a unique ID built from: CATEGORY-FUNCTION-TYPE-NUMBER (e.g. IT-SEC-POL-001). This ID is permanent and does not change on edits.
π’
Version Numbering
Versions follow MAJOR.MINOR format (e.g. 1.0 β 1.1 β 1.9 β 2.0). You choose whether to increment the version each time you save an edit.
π
Version History
Every version increment creates a history entry. Click History on any document to see all previous versions, change notes, and file links.
π
Review Cycle
Each document has a review cycle (months). When saved, the next review date is automatically recalculated from the save date.
π₯οΈ Asset Register
π€ User Management
| Username |
Full Name |
Role |
Status |
2FA |
Last Login |
Page Access |
Actions |
| Loading... |
β System Settings β Mirador Sync
β System Settings β EOL Check Schedule
EOL check runs independently of Mirador sync. Recommended: schedule after Mirador sync completes.