Policies are written, approved and sealed.
The document lifecycle: versions, approval steps, publishing, read acknowledgements and annual review reminders.
Take a document from draft to published: approve the steps, watch the read acknowledgements.
Main screenThe document lifecycle: versions, approval steps, publishing, read acknowledgements and annual review reminders.
The problem
Information-security policies drift around shared folders: which version is valid, who approved it, who read it and when it is due for review are all unclear. The audit asks for "proof of reading" and it cannot be found.
What I built
Mühür versions every document in GLPI; approval steps are defined around segregation of duties, and the final approval generates a PDF and publishes it. Staff see only published documents and acknowledge that they have read them. As the review date approaches, a reminder and a ticket are created. Documents link to processes, assets and risks.
Technical notes
- The manager is resolved at approval time and written into a snapshot
- Annual review opens a ticket through cron
- Links to process, service, application and risk records
Highlights
- Versions stored as GLPI documents; rich text or file
- Configurable approval steps: role, group or the author's manager
- Publishing: PDF through LibreOffice, in-browser viewer
- Read acknowledgements, exceptions, bulk add
- Ready-made document lists per regulation (SPK, BDDK, EPDK, ISO)