Just because you're a Network Engineer or an IT Administrator doesn't necessarily mean you have the right to stick your fingers in the Group Policy pie. This is not uncommon in larger organizations who wish to have a tight control over people's access level. In fact, security best practices do dictate that power and control is distributed among several individuals so that the company has checks-and-balances. Just like our government is split into three bodies in order to restrict power, making sure an individual administrator has only limited power can provide some counter-measures, just in case the guy who runs things has a bad day and decides to barbeque some servers.
The practical aspect of this is that to deploy URA, someone will need the permissions to create the Group Policy objects. If your account has full permissions on the domain to do so, then you don't have much to worry about. During the setup, when it's time to create the policy, the...