Document-level user privileges

Hi,

Another question. I would like to have a document tree that looks something like this:

>Products (admin editable)
>>Product Area 1 (Group 1 editable)
>>Product Area 2 (Group 2 editable)
>Services (admin editable)
>>Service Area 1 (Group 1 editable)
>>Service Area 2 (Group 2 editable)

I can’t seem to find a way to set this senario up however, because it seems that editing privileges cascade somehow (Is this right?). So it seems that even when I set Group 1 to be able to edit Product Area 1, they are unable to see the files, because they are a child of Products, which is only editable by the admin group.

So in order to have users in Group 1 edit the children of Products I have been having to set Products to that Group, even though they should not be able to edit the main products page (which most likely has ditto listing calls they shouldn’t touch.)

Am I missing something or is there a way to make individual pages editable by a group regardless of their parent?

Thanks again.

anyone?

This should be more readily controllable in the 096 release. When the final rolls out there will be a tree menu viewing option for controlling whether or not you can see documents in containers that you don’t have rights to edit; prior to 096 they would simply be invisible documents.

I too will be waiting for this implementation!

Oh great! I’ve been waiting for this too!