Problem in Branch settings

Hi,
I am trying to give author role to tow groups on a branch.
In that branch there are two folders and I want to give edit permissions of first folder to the first group and second folder to the second.
But even after giving read permission to the other group, all the groups are able to edit all the files in both the folders.
Am I missing something. Or this is not possible

We are using TeamSite 6.7.1 (Windows)

Find more posts tagged with

Comments

Migrateduser

In the scenario you describe, you need a third group. Use that group as the group for the authors, and use your current two groups to secure the permissions on the folders. You'll want to adjust your submit.cfg to enforce those permissions.

chiragjain

Oh Ok,
I wanted one clarification. Suppose I give author role to two users on a branch, so is it true that they will have edit permissions on all the folders in that branch, even if i dont provide full control to them on the folder.

nbwoven

I believe branch permissions will supercede folder permissions so having a third group is good idea .

Adam Stoller

Oh Ok,
I wanted one clarification. Suppose I give author role to two users on a branch, so is it true that they will have edit permissions on all the folders in that branch, even if i dont provide full control to them on the folder.

Branch and workarea permissions get the user into the area.
TeamSite roles determine what actions the user is allowed to perform within the area.
File and directory permissions determine what actions the user is allowed to perform on the file or directory.

With the possible exception of Master users, if a user is a member of the group-for-sharing for a workarea but not a member of any group (or owner) with access to a specific file within that workarea - they should not be allowed to edit the file. If they don't have any OS-access to the directory, they generally shouldn't be able to navigate into it, but that might still be allowed (although I seem to recall that there was an iwproxy setting to enable access checking that might prevent that too).

What TS will not do - is hide files or folders to which the user does not have OS-access. It will hide branches and workareas (if that feature is enabled in iw.cfg), but not files and folders within the branch / workarea.