Granular control on checkout setting
A document's checkout setting applies to whoever has access to the respective document. However, the checkout requirement may be different for different roles. For example, not everybody is required to actively accept new revisions of the OM Part B (for example, the CAA).
It would be, therefore, beneficial if the checkout setting could be bound to specific roles as defined by the editor or admin.
0
Comments
Hi Bruno,
Thank you for the suggestion.
I completely understand your perspective and the value it potentially adds.
We will not be implementing this functionality any time soon though. The reason is that it would add several layers of extra complexity and maintenance to the system from the admin side.
In the future if we can think up a good way of handling this without adding too much complexity, I will be happy to see it implemented.
Keep the good ideas coming :)
Please sign in to leave a comment.