We've made some improvements to how role permissions are managed, and hope you like them! 

1. Changes to infrastructure permissions

In the Role / Permissions tab, role permissions can now be set on different infrastructure components in Heropa. Previously, this was managed by an overarching category called 'Infrastructure'. 

This has been replaced by new separate permission categories for Environments, Templates, VM Images, Policies, and Public IPs, example below:

Permissions can be set on each of these individually, to allow for more granular control. Note that in some cases, where the categories are related, selecting a permission in one category will automatically select a permission in another category. This is because the functions are dependent on each other.

2. A new way to manage what's visible in the left navigation

The new 'Left nav' permission is what determines whether the category is visible in the left navigation menu in Heropa. This can be used to control what screens users with different roles see. Note that there may some roles where permissions to a category might need to be granted, even if seeing the screens in the category is not required for the role. 

For example: You might want to give a role left nav visibility of Courses. If the role also requires visibility of the Environments, Templates and VM images in courses, then a 'View' permission should be set on each of these categories, even if the 'Left nav' permission for these categories is not set. 

Learn more in our knowledge base article: Using roles and permissions.