Good evening,
We have an issue that VMware support seems unable to help with (and they suggested asking in here).
We just started using Orchestrator (5.1) and we have people that only have access to specific (e.g. their) virtual machines. We have no problem giving them to the appropriate permissions to execute workflows on those VM's. The problem involves giving them permission to *select* virtual machines inside workflows.
For example, let's say you want to allow a user to utilize one of the built-in Shutdown Server Workflows (and they have permission within vCenter to perform that action). When they choose the value for VC:Virtual Machine it brings up vCenter Server. If you navigate to the VM folder there is no "expand" option unless the users has access at the datacenter level (and we can't allow customers access to view everyone else's servers).
We've gone back and forth with vCenter Orchestrator and vCenter Server support. vCenter Server support agrees the permissions are correct because you can login as that user and see the folder and VM.
We've tried creating authorizations and that's very helpful if you give permissions to a specific VM for a specific workflow and function, but we really need our customers to be able to create their own workflows for their own vm's without seeing everyone's virtual machine in the entire environment.
Does anyone have any thoughts or suggestions on this issue?