Hi,
I work with ISO management system documents and maintain isochecklist.com. I am looking at CryptPad for a small controlled document library, but I have not deployed it yet.
The workflow I am trying to create is quite simple.
Once a document is approved, normal users should continue to see that approved copy. Editors should then be able to work on the next revision without changing the version people are currently using.
I would like to keep:
- one approved copy that is read-only for normal users
- one working draft for editors
- tracked changes or suggestions for reviewers
- the name of the person who approved the revision
- the approval date
- access to earlier approved versions
I saw that the Document app supports tracked changes. What I am not sure about is the best way to separate the approved document from the next draft.
Would you normally duplicate the approved document into an internal team drive and continue editing the copy?
If so, is there a clean way to keep one stable public or read-only link pointing to the current approved document, then replace that document after the next revision is approved?
I would prefer not to export and upload a new PDF every time, because that would separate the document from its comments and history.
The main questions are:
- Can an approved document be locked against editing without removing its history?
- Can reviewers still see the draft while normal users only see the approved copy?
- Can the approval decision be recorded inside CryptPad?
- Can the public link remain unchanged when a new revision becomes current?
For context, I maintain this page on document revision and approval controls. It is my own page and only explains the document management requirement behind the question.
Has anyone built a similar workflow in CryptPad?
I will test the suggested setup and post the final folder and permission structure here.
