Under Community Review

The fact that CM does not inform the parent visibility scope is not nice, but I doubt if it should prevent you from selecting some other publications. Keep in mind that a single group might be used in several parent groups with different visibility scopes. More to that, effective visibility scope is determined not only by the immediate parent group but also by all parents if there is a complex hierarchy of nested groups.

The practical approach might be to highlight the current set of effectively visible groups in the UI, but do not prevent from selecting other publications if needed.

In any case, let's keep this idea in the under community review state to collect more votes and comments.

When using Sub User Groups, acknowledge the parents group 'Visibility' scope when setting up the child group (inherit visibility scope)

When the parent group has a visibility for only several publications from the hundreds available, the child User Group should only see the visibility scope so it cannot select publications outside the scope of the parent.

Ingmar Umans

  • I think Ingmar has highlighted a valid usability issue. I also agree with the community review comment that perhaps just making it impossible would make for difficulties in related use cases. It might be worth thinking about a total redesign of the Users/Groups UI. It's been more or less the same since R5 GA, when scopes were a late addition. It works well enough as long as you don't turn all the dials at once, but I'm not sure if small tweaks will be the solution.