Is it possible to provide access to Teamsite User ids according to folder strucuture?

I want to provide the access rights to Teamsite6.5 userids according to the folder structure instead of Workareas. Currently access is provided according to Workareas (general_wa)

Teamsite Structure:

/default/main/TRAINING/ETC/WORKAREA/general_wa/templatedata/general/en/data/HR...

/default/main/TRAINING/ETC/WORKAREA/general_wa/templatedata/general/en/data/IT

I want to provide access to user ids according to the folder (HR,IT)

Pls suggest how I can do this..

Thanks
Anu

Find more posts tagged with

Comments

nbwoven

Well I assume you're on TS6.7.x so just create OS Groups and add users to it.
Eg. Group G1 & G2 .Add users for HR & IT . Then navigate to that Folder and through Folder Properties give the Group access to that Folder(Not WA) ..
Explore the Add Permissions / "Remove Inherited Permissions" to suit your requirements

Aadi

Yes, you can control the access level upto folder/file only through OS as nbwoven described above.

curiousmaverick

Not possible till TS 6.5...

Adam Stoller

I want to provide the access rights to Teamsite6.5 userids according to the folder structure instead of Workareas. Currently access is provided according to Workareas (general_wa)

Teamsite Structure:

/default/main/TRAINING/ETC/WORKAREA/general_wa/templatedata/general/en/data/HR...

/default/main/TRAINING/ETC/WORKAREA/general_wa/templatedata/general/en/data/IT

I want to provide access to user ids according to the folder (HR,IT)

Pls suggest how I can do this..

Thanks
Anu

Permissions at the workarea level provide access to the workarea.
Permissions at the file and directory level are used to determine the ability of users to read / edit those files and needs to be done via OS commands / interfaces and can be maintained via a well written submit.cfg - and this is pretty much the same way it's been done since 3.x days if not before.

In 6.7.1, the TS GUI provides mode access to interacting with file-level permissions, but the same basic principles apply.

Migrateduser

Is there a way to restrict a user not allow creating sub folders under folder.
I am aware at role level we can set this option. At folder level is there away?
Do not want to create more roles. Please let me know...

Adam Stoller

Is there a way to restrict a user not allow creating sub folders under folder.
I am aware at role level we can set this option. At folder level is there away?
Do not want to create more roles. Please let me know...

Theoretically you should be able to restrict it at the OS level - but I'm not sure if that will work (haven't tried).
If this is particularly important to you - I suggest contacting IWOV Support and see if they can assist you in determining if it is possible (and how) or have them open up a feature request

Anujap

Thanks!!

I contact to Interwoven support team, and following is the response from them..

We can give the folder level access to the user ids only in case of new file creation/edit the existing file through UNIX group(Means a user who don’t have access on particular folder does not able to create or edit the files in particular folder but user can submit the existing file and we can't restrict submit option.

Thanks
Anu

stya

Hi ,

I have a scenario where I need to restrict a particular folder under workarea.

But this folder is not a part of template data.

say,

WA
images
press

Now If I need to restrict this "press" to a particular group "media" which is a teamsite group.

Is it possible?

Thanks,
stya

Adam Stoller

Hi ,

I have a scenario where I need to restrict a particular folder under workarea.

But this folder is not a part of template data.

say,

WA
images
press

Now If I need to restrict this "press" to a particular group "media" which is a teamsite group.

Is it possible?

Thanks,
stya

Yes it is possible - this is generally covered in the TeamSite Administrator's Guide and/or TeamSite Administration training - permissions for files and folders within the workarea is controlled at the file system level - you can usually modify such permissions through CLTs or the GUI, but if you want to make sure its persistent across all the files in that directory you should also look at the documentation on the submit.cfg file (also in the Administrator's Guide)