I'll pile on here. Your job is no longer to be the sysadmin, or even the BOFH - your job is to develop the projects, policies, etc. that the IT staff will implement, oversee the implementations, and ensure they transition to operations successfully - all the while planning the next move. You shouldn't need admin rights in an organization that size.
You SHOULD, however, have authority over the people doing the implementation and administration. If they work for you, or you have significant enough levers on them, you can exercise oversight. As another respondent mentioned, getting read access is simple, and I agree with that completely. Setting up a lab where you get deity rights is simple enough, and you should do that in your first year, but for the operational environment, you shouldn't ever have to sudo. You now have people to do that.