Nested group behavior and workarea access

System

Hi DevNetters -
This question relates to our Solaris 6.7.1 (patched, but no service pack) TeamSite installation:

We've been cleaning up some of our 'organically grown' TeamSite groups to arrange them more logically, and ran into this behavior:

We set up a set of groups of users, like Editors1 and Editors2 for example.

Then we added both of those groups into another group, let's say EditorsAll. So, EditorsAll contains Editors1 and Editors2.

We then set up a workarea shared with the EditorsAll group (allowing access to the workarea to all of the members of EditorsAll) and finally set up a mapping of the EditorsAll group to the Editor role for the branch.

We expected that this setup would allow allow of the granular members of the Editors1 and Editors2 groups write access to the workarea through their membership in the EditorsAll group, but this turns out not to be the case. We ended up needing to map the Editors1 and Editors2 groups to the Editor role of the branch.

Have any of you run into this scenario and does it change it any subsequent releases of TeamSite? We'd rather just manage the subgroups of the EditorsAll group to control the Editor access to content.

Thanks all -
Wally Box
Nike, Inc.