nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Folder level permissions

tamz

iam trying to restrict the access to folder level in a workarea.lets say, i have four folders f1,f2,f3,f4 under a workarea W1 and i have two groups g1 & g2. g1 group users should access(/edit) all the four folders in workarea whereas g2 should access only fi,f2 and rest of folders (f3,f4) should be readonly to g2 users.

Followed the below steps and still couldnot achieve it.
*Assigned editor role to both the groups g1,g2 in a branch.
*Added g1 as owner to workarea w1 so that g1 group users can access all f1,f2,f3,f4 folders.
*Added g2 to folders f1 & f2 with "full-control" permission. but still g2 users are unable to edit the foldersf1,f2.

Any suggestions to achieve this requirement are very helpful. Thanks in advance.

Teamsite 6.7.1sp1, windows platform

Note:i read that users cannot edit files/folders if they are not members of group owned workarea.

Find more posts tagged with

Comments

tamz

Even the below mentioned approach was not helpful.
*created a group g3 and added groups g1 and g2 to it.
*Added g3 as owner to workarea w1.
*Removed inherited permissions to f1,f2 folders and added g1 to these folders with "full-control" permissions.

Now, as expected, g1 users can access all folders and g2 users will access only f1 & f2 folders.

But in-live scenerio, there would be 100's of folders in workarea and removing inherited permissions to those would be tideous job. and also same job to be done whenever a new folder is created. This sounds more manual and looking for better approach.

thanks for your suggestions. Smiley Happy

srosewall

This sounds more manual and looking for better approach.

Hopefully a helpful nudge - have you had a look at using submit.cfg?
If you're not familiar, then I would suggest taking at look at the TeamSite Admin guide.
Submit.cfg allows you to define access control on folder/file patterns and applies the ACLs you define automatically when folders/files are submitted.

Hope that helps.

Regards,

tamz

thanks for responding..
Folders available in workarea are already submitted to staging area and submit.cfg will not apply the rules if the files/folders are already submitted to stagingarea.

ISCBorisB

Folders [...] are already submitted to staging

So? Make sure that your WA has all latest and greatest content, do "Get Latest" etc. Publish an Edition so that you have
a failover copy. Create a temp Workarea from that Edition, delete everything and submit Deletions. The end result is an
empty Staging. Then get to your original WA and Submit all overriding conflicts