Projects are defined through folders and it is possible to apply a lifecycle to know what the project state is. For example “opened”, “closed” or “archived”. Then to be sure that all documents within the project tree is unavailable for any change, the security rules are overridden to be aligned with the project change.
When the project state is changed to "CLOSED" then the sub folders are closed as well. To apply and override the security rule to all files the option "Security for files inside folders" is activated and "Apply folder's security to its files" is set.
But in some case, the project must be re-opened. Unfortunately, when the project is re-opened, it sounds that the rights and the security is not set back to the original setting even if the option "Clear security override from files inside the folder" is set during the transition. The document security setting that we defined through the life cycle is not reset and we don’t get back the original security setting when the project was initiated.
The idea would be to have an option to get back to the original security setting by removing all security elements due to another change. We are able to change the documents security setting. But we are not able to get back to the document original security rule.
