Role based vault access inheritance
FMCU System Admins
We have noticed that if a Role has Full Access to a sub-folder in our organization vault folder structure that the top-level folder(s) change to "Navigation". I understand the logic, however, when adding a new folder that's in the path of the Role's permissions, the Role is granted the permission of "Navigation" on the folder. This is undesirable behavior for RBAC. We would rather not have this behavior occur and the new folder default to "No Access". I have included screenshots that I hope will help visualize the expected vs actual behavior.