But to protect the test team's "expert" scripts, put them under code control and only give the users outside the department Read-Only access to those scripts.
I guess I would not discourage anyone who has access to QTP from trying to learn QTP and write scripts. Even if they are not successful (which seems pretty likely, given the complexities of this tool), those attempts could indicate a new script or set of scripts that the test team has not considered--and could be scheduled for their expert implementation later.
Well i achieve that by emails. I have a tool which i want to be available to everyone but the access method should be simpler and black box to the end user.
So they send a email with a special subject line to my id which in turn activates a script in my outlook -> activates a script on the my local -> activates a script on remote machine -> Runs QTP -> Remote script emails back the result.