Having had a look at that now, I would have to disagree. If it did work as you said, which is pretty much the defaults, then everything would be just fine.
Here is the problem:
If 'Perform Operations to any call' is not selected, then no operations can be performed to any call, including your own.
If 'Can see group calls' is not selected, you can't see your own call to do anything to it.
If 'Show calls to group members' is not selected, you can't see your own call again.
So I was hoping in the first instance that the default behavior would allow operations to be performed on your own call.
In the absence of that, I was hoping that not showing your call to others, or not having others viewing your call, would stop people operating on the wrong call.
It appears that the group rules work as described, but completely omit the distinction of 'Self' as part of the group rules. When you are not showing or viewing group calls, this includes yourself and no active calls ever appear.
It's V12 SP2 on Server 2012. No updates outstanding. Running on Windows 8 and Terminal Server 2008 client machines.
Unless someone knows something else, it's an 'all or nothing' access to operations in the presence panel. Not really ideal for those careless mouse operators, who will not be able to have it at all until it can just operate their calls only.
It has to go in as an upgrade to V11 tomorrow. The very users best not trusted with full access to all calls are the same ones who will have trouble using hardware for transfers. So not really an ideal situation.