Tailor the views for observer role with a defined scope to only show the entities defined in the target group

Integration:  On-prem VMware integration.

Entity type: Virtual machine

In large enterprise, the hypervisor, clusters and nodes are maintained by a centralised team. This team is responsible for automation, moving VMs to remove contention, maintain compliance etc. Multiple customers own the VMs that run on these shared environments and the owners of the VMs are responsible for the resources required to run the applications on these workloads. As an example, the customers could include HR, Finance, Operations etc. These customers do not have permissions to move VMs or perform operations at the ESX host, cluster level. They can however, take actions to add/remove memory/cpu to their VMs.

Current Situation: When a user with a defined scope (static group of VMs) logs into Turbonomic and clicks on the "Action" menu, the recommendations shown are not limited to the VMs defined in the static group. Instead, the recommendations shown also include other VMs that run on the underlying hosts that host the "in scope" VMs. However, in an environment with 100s of VMs, the owner of the VM would not be able to differentiate or know which of the listed VMs belong to them and which ones are for another customer base. This is key, as the customer would have not have accurate insights of the VMs they are responsible for.

Requirement: When a scoped user logs in, the "action" menu only shows recommendations for operations that apply to the group of VMs that the individual is responsible for. However, include a flag/toggle that allows them to see any "move" operations too so in the event of any resource contention at the host level, the customers can take the recommendation to the central IP team responsible for the hosts/clusters. Likewise, the view should not be restricted to just the VMs. The customers should be able to view the recommendations for the right sizing of the VMs for an entire application/business service etc. based on the supply chain but this should only include VMs the customer is responsible for and exclude anything else that's not in the scope.