You are correct, it is not possible today to grant permissions to all processes in a category in an easy step.
It has been requested before, but hasn't made it into a release yet and is not currently on the roadmap.
There are 3 types of security permissions that Orchestrator has today, for creating "Roles":
- Object List is the most straigtforward one. You can explicitly add/remove processes to the list for which you want to grant permissions. It is straightforward, but also the least dynamic. So you would have to remember to add/remove to the security role as you create/delete processes
- Object Type is very dynamic, but it is also very broad. You can use it to grant permissions to **all** objects of a specific type
- Owner Security is dynamic and could give you what you want, but it still requires paying some attention how you create and manage your objects.
You could try Owner Security to give you what you want.
- Create a security group (any group would do), let's say group A.
- Set Owner field to group A in all objects (processes, targets, categories, whatever), to which you want to grant permissions to.
- Now create a Security Role and add Owner Security Permission to that role, whose owner field is also set to group A.
Choose object types/operations that you want to give permissions over. Now you can assign this role to other people.
This role will be dynamic: meaning that as you create new objects and set their Owner field to group A, the users who are assigned to the role will automatically get the permissions over those objects.
If you decide to go that route, you can also utilize a little know option in the UI, that allows the user to set the default value for the Owner field in the newly created objects (check Security tab under Tools | Options menu item).
Also, keep in mind that the default security Roles grant full control to "owners" of objects. So if you want to avoid that, you might want to keep the security group empty or modify the default roles.
Hope this helps.
