@Aram The Primary goal is to give Operations the ability to Stop any “rogue” actions, and potentially deploy actions to any computer in the event of an emergency. The use of “Four-Eyes” authentication is more an attempt on my part (at the request of our ISO) to keep the Operations folks in check a bit when it comes to using their MO accounts.
The scenario I’m dealing with regarding Stopping of Others Actions is that we have a LOT of Roles defined in our environment and I’ve had trouble getting Action stopping to work properly in all cases with some of the Console Operators. Documentation indicates that you need to have matching Roles for the ability to stop another Console Operator’s actions, and up to now, I’ve not tried adding someone to ALL the Roles.
If someone can tell me that simply adding the Ops folks to ALL the Roles would resolve the issue then I would be thrilled!!! My concern then is Actions deployed from content is in a Console Operators Personal site. Would Operations be able to stop those actions?
I would LOVE to find a way to keep Operations out of the Master Operator role if at all possible.