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; } } }

Restrict Permission to files/folders within a workarea

rwinterpacht

I am having quite a time trying to get this to work, I figured it would be a little more cut and dry...but unfortunately not the case...

I have a shared workarea, where the workarea is shared by a group that contains all of our editors we want in the workarea.

I have a folder that I only want certain groups to work in, so I have a submit filter that sets the permissions on the files/folders. If a user isn't in this group, I assume they shouldn't be able to edit. But since they are a member of the TS group that shares the WA, they DO get access. How can I restrict this? All I see for permissions so far is either all or nothing...

On a Windows 2003 Server, TS 6.7.2 sp1.

Any recommendations or best practices are welcome!

-Raf

Find more posts tagged with

Comments

Adam Stoller

Check the actual folder and file permissions at the OS level - don't rely on what it shows you within the TS GUI.

rwinterpacht

Well, here's how I'm testing it out. The GUI does in fact show the correct permissions on the files and folders. The submit filter is applying the group permissions correctly...I'm using a test account that is NOT a member of that group still has edit rights in CCStd.

I'm more of a Unix person, so it may just be a matter of correcting it so that the Windows equivalent of "everyone" has only read access. I may be able to try this in the submit filter, as well (0664, or 0775 for dirs). I'll try it...

Thanks!
-Raf

Adam Stoller

Well, here's how I'm testing it out. The GUI does in fact show the correct permissions on the files and folders. The submit filter is applying the group permissions correctly...I'm using a test account that is NOT a member of that group still has edit rights in CCStd.

I'm more of a Unix person, so it may just be a matter of correcting it so that the Windows equivalent of "everyone" has only read access. I may be able to try this in the submit filter, as well (0664, or 0775 for dirs). I'll try it...

Thanks!
-Raf

You cannot use Unix masks (0664, 0775) on Windows - you need to use the ChangeAccess / SetAccess options in submit.cfg for that -- also, once a directory has been submitted, you cannot change its settings via submit.cfg - only from the file system -- or remove / rename the directory, submit the deletion, then create the directory and submit it with the proper submit.cfg and it should get the correct rights.

Also - be sure you're using an account that only has Author or Editor rights on that branch - Admins and Masters would probably invalidate the verification.