Thereby proving you've never worked in IS.

The #1 rule in IS is "trust no one", particularly if it's a production system. The right way to do it is to develop on one system, test on a second, production is a third. Developers move freely between development and test. Test is kept as similar to the production system as possible. Only senior IS people - often only two admins per box, and one of those is just a backup - actually have access to move things from test to production. Anything less is too risky.

The correct solution to the problem is to have IS install the needed module on the production system. They SHOULD do that, if you can show that it's necessary and safe.

- Ozymandias