I'm currently investigating how to, with as little effort as possible, provide a web portal to trigger workflows.
Currently I'm trying to find a way around the fact that the root-level permissions, which are required to log in to the weboperator, are auto-inherited across the entire hierarchy, meaning that anyone who can log in to the portal will see *every* workflow in the entire repository.
Is there any way to hide this? Or choose which workflows can be viewed inside the web operator?
Yes, removing the permission on all child folders and adding it back on just the workflows I want to publish would probably achieve the desired result, but that's just nasty.