Restrict Access within a workarea

MrShake

We are upgrading from 6.5 to 6.7.2 and in the process eliminating a ton of extra workareas in hope that the 6.7.2 users and groups will allow the level of security we need.

Example Structure

Branch A
-Workarea A
-Folder 1
-Folder 2
-Folder 3

I want to setup 2 groups:

Group1
Group2

and give them access to specific folders, example:

Branch A
-Workarea A
-Folder 1 - Group1
-Folder 2 - Group2
-Folder 3 - Group1 and Group2

I've tried setting group permissions and inheritance and it doesn't appear to do what we need. We need each group to only see the files/folders they have access to, and to mask those they don't. As well, with the permissions I thought I was setting, even if Group2 has no inherited or direct permissions on a folder, they can still edit it unless they are not part of the owning group for the workarea. If they are not part of the owning group, they they can edit NOTHING in the workarea at all, though they can still see everything.

Help?

Adam Stoller

Based on your example you need three groups:

Group-C should be the group that shares the workarea, Groups A and B should be configured for use in the submit.cfg to ensure that the files and folders get the correct access rights set to them, as well Groups A, B, and/or C can be used to set Roles for the branch.I haven't played around with security settings too much lately. In the past there were issues with restricting access to files and folders within a workarea if the user had access to the workarea - I believe those issues were fixed but, as I said, I can not verify that.If you set things up correctly, and can verify / document that you have them set up correctly, and people do/don't have access to files that they shouldn't/should - you can open a support case for it.