vROPS 8.0 Custom Group Not Showing For All Users

[Bgark_99]

We are using vROPS Version 8.0.1.15331180 and have created some custom roles for different permissions. One has additional content admin access above the other one which is primarily for reporting. We want both roles to have the ability to create and manage custom groups in addition to the other functions they will do. Both roles have been defined with all permissions ticked (Create / Delete / Edit / Read) under Environment – Custom Groups Management. Separate users have been assigned to each role. I have tested this by creating custom groups under the Function grouping using both users and this works. However the user with the lower access role assigned can only see the custom group that was created with their userid under Environment – Groups and Applications – Custom Groups - Function. This user cannot see (or search for) the custom groups created by the user with the higher access role assigned. The user with the higher access role assigned can see all custom groups that they created and the lower access user created. 

Is there any reason why the above could occur when they have the same Custom Groups Management permissions assigned? Are there any specific permissions when creating a custom group that enables others to see it as I could not identify any?

[ScottThomson]

Hey mate

You are correct, I have seen this behaviour also with dashboards.  You will need to do a comparision and just keep checking what permissions you want the lower user to have.  It might be a pain if one user is GOD and one is a pleb.

It could be

Administration - Configuration - Group Types Management - View, Create, Edit, Delete.

Im not sure tho, I havent gone that granular with that as yet, im the only god and the rest are RO 🙂

Good luck

[RickVerstegen · Accepted solution]

Do both users have object access to the custom groups when setting up those permissions? Also check the "propagate" checkbox.

[Bgark_99]

Thanks Rick. The problem was that the lower access users did not have Object Hierarchy access to Custom groups despite having the permissions ticket to see / management them. Once this was fixed it is working.