Restrict users from changing finally approved document

[Entmatix]

Thanks for the great software, guys! Always nice to see how good FOSS can be.

As for workflow feature you implemented not long ago I'd like to add a little option. I think it's crucial since we are dealing with multiuser software. I'm talking about locking (preventing from any further changes) of a document that has passed final step (stage) in workflow.

Say you have a workflow that includes multiple users (user0, user1 and user2) and you set up only read permissions for these users (no tags used in this workflow). User0 sent a document that goes to user1 and then goes to user2. After user2 approves the document (last step, it should be final) it goes to user0 as approved. User0 has all the bells and whistles: to modify the metadata/document itself. Even change tags. I think this freedom simply contradicts with the very principles of such workflow and software. If someone makes a final approvement, the document must stay unchanged.

Could you please implement at least an optional locking of document after final approvement in workflow? Thanks in advance!

[sailhobie]

Yes, I am also interested in something like this.

[Entmatix]

As a workaround I use gpg signs. Last user in workflow sign document with users gpg signature and attach the signature to the file. It doesn't prevent file modifications and it doesn't work with non-document workflow (when you approve simple text message), but at least it allows to check whether a document was modified after approval.

[madduck]

This definitely sounds like a useful feature to have. GPG signatures are good, but quite cumbersome in their use in this case. I.e. first I'd have to suspect that a document was changed before I'd even go through the trouble to verify it.