Issue link: https://resources.cloudbolt.io/i/1443939
8 Individual Group or User Policy Assignment: In the previous example with the template business group, we had those base level ac ons, but we also had requirements where we would create specialty en tlements within a business group to en tle specific ac ons above and beyond the base en tlements that all users would see. These specialty en tlements would then be assigned to individual users or a Security Group in the Business Group that held a subset of the users in the business group that were o en not administra ve level members. In vRA 8 policies, there is currently no mechanism for assigning granular permissions to a subset of the members or administrators in a project. Policies are applied to either Administrators or Members of the project. Catalog Item Policies: When you go to create a new policy, you may no ce that the capability to restrict access to Catalog Items in vRA 8 is no longer available. The only op ons that you are presented with are Lease Policy or a Day 2 Ac ons Policy. It seems that Catalog Items are en tled to the project as a whole and there is no way to filter the available Catalog Items on an individual user basis. Quite a few of the customers we work with require the ability to restrict access to not only 2nd Day Ac ons, but to Catalog Items as well within a project. VMware has made massive strides in many areas to improve upon user feedback from past versions. Cross-Cloud capabili es are markedly enhanced in the new version, and Infrastructure as Code is now a reality for vRA blueprints. Whether your first foray in the vRA8 world, or you've worked with vRA since the DynamicOps days, there is a learning curve ahead. M I G R AT I O N G U I D E