Agreement creators and Secured Objects - How to block admins?
Here is a thought exercise for you. Best practice is to never have a process where some one can create a request and approve their own access. It should be a two step, two person process. Take agreements for example. With this rule, I can setup a single approve/reject workflow for a data owner to approved access to secured documents through agreements. The data owner however, cannot create the agreement or initiate the process. This works perfectly and can be done via ACLs. I found I need to at least grant read access for the data owner to see the agreement but it did move it through its lifecycle to the approved state.
I also found that I need to bootstrap the data owners own access via a context-based agreement. I made an open ended agreement for the data owner to view anything that is in their context. For anyone else, the data owner can allow in too via this method. I know system states that you should use the labels unrestricted group to do this but does that not mean the data owner can view data in ALL contexts that label is set? Not good.
Currently, I have the agreement managers group set to be the unrestricted group for my two labels. For items specific agreements, the creator of the agreement must be able to see the object they are adding to the agreement. I am thinking what would be the case if they were not the same groups.
Here is the question: How can I have an agreement manager, someone who can create and agreement (the access request) complete their task BUT not themselves be able to see the data since they do not have a need to know? Same is true of many IT functions that are granted access to see everything on the network, all folders, etc.
