enforce operator role "hierarchy"

[dustymc]

Help us understand your request (check below):

• other

Describe what you're trying to do

Another sidetrack of the object tracking group: some roles have dependencies (eg container stuff, but also everything relies on coldfusion_user first existing), these are documented, can/should they be enforced?

Benefit: occasional slightly-less-confused manager (??)
Cost: Not sure this is possible, not entirely sure things are truly linear/hierarchical

[mkoo]

Benefit: occasional slightly-less-confused manager (??)
Cost: Not sure this is possible, not entirely sure things are truly linear/hierarchical

Not sure if it is possible stick to the hierarchy rule but if the opportunity is there we should organize permissions with some logical order. eg. view-permission--> edit-permission--> manage-permissions-- >admin-permissions which should also reflect the descending number of users with those permissions.

this came up in a (useful) rabbithole in the object tracking meeting!