Ah. Forgive me for not paying attention to that requirement. Tools usually
run as the Galaxy user so only local admins can do that at present because
allowing a non-admin user to install a newly generated tool, especially on
a public site opens up some interesting security challenges. I think it
wo
This doesn't seem to fit into the use case that my colleagues have described to
me. Our tool, used within Galaxy, creates/builds/generates new tools for Web
service operations. Once a user uses our tool to generate a Web service tool,
it should be visible and usable to them.
Currently, in or
