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

Teamsite permission

madmax

hi all,

I have an admin workarea and i want to give access to one of the image folder to a group where they can -
1) create files
2)delete files
3) edit files
4) and all other task that an editor usually do.

Workarea's Teamsite properties:
Sharing : Group
Owner : server\iwadmin
group : server\TS_admin

That image folder has the following teamsite properties:
Owner : server\iwadmin
Group : server\none
Permissions : server\TS_admin:Full Control (All), server\imagegroup: Full Control (All)

Now when the users from the group server\imagegroup went on the image folder under admin workarea ,most of the item from "File" and "edit" menu is grayed out.For instance new folder, edit , etc.

Any ideas to resolve this issues?

Find more posts tagged with

Comments

reddyl

Check the parent folder permission for the group.

madmax

my directory structure is below :

//server/default/main/press/WORKAREA/workarea/Image

branch: press
workarea: workarea
Folders: Control
Include
Image
Log

So when you say parent folder group permission -- is that "press" you are talking about?

ravio

For performing the actions you described, you will need to figure out
1. workarea permission
2. asset permission
3. role based permission

It might help to create a table with all that info.
The TS Admin guide covers this in detail.
Look up the Managing TS Access section.

bpg

If you're adding a new group to the writable workarea, then you'll need to force the propagation down through the folder structure.

Do this by going to the Properties of the workarea folder and going to Security -> Advanced -> click the Replace Permissions entries... tickbox and then click Apply.

HTH

Brendan

madmax

Workarea can be assigned to only one TeamSite group and without workarea permission no user can use all the TeamSite "new file, new folder, edit, etc" functionality. To get the workarea permission they need to be in that workarea group. My case that workarea is only for TS_admin. If I add certain user to that TS_admin group, they'll be able to make changes to other folder under TS_admin workarea too which I don't want to.

Can I have more then one group assigned to TeamSite workarea? Manuel does not say anything about it.

I tried iwchgrp which does not let me assign more then one group to workarea.

Migrateduser

I haven't tried this, but maybe you can create a group and add the other groups to it, then assign the newly created group to the workarea.

madmax

It won't solve the problem.

Because you are not allowed to add a group under a group in windows group.

chunk

You'll need two separate branches for this to work. You cannot do this only with separate workareas or directory/file permissions in one workarea. Or, at least you can't in TS 6.5 on Sol 2.9.

I have the same issue. A website that i want a group of people to have write access to a subfolder. We have all content in one branch, many workareas. All directories inthe workareas are 775 for me except the one subfolder which is owned by and shared with a different user/group.

THe problem is that since the users own their own workareas they can create files and directories anywhere. Once the files are submitted, they get the proper permissions through submit.cfg and then they are locked out. But the files are already created.

The only way that I've found to solve this is to give them their own branch. They create anything they want in the root of the new branch/workareas. When they want to deploy to the website, the workflow simply deploys their stuff one level lower than the docroot.

I have two other groups that I need to setup the same way so if anyone has a better suggestion please let me know before i make the effort! Smiley Happy

Good luck,

chunk

Adam Stoller

If I understand the problem correctly - it is possible to support the scenario.

Consider one "global" (not necessarily Windows "global" - the generic meaning) group for which all members have access to the workarea.

Then consider separate groups - that contain subsets of the membership of the "global" group - that are given explicit access to sub-folders within the workarea. The permissions for the directory need to be set at the OS-level and should be re-inforced by the submit.cfg file. Also - if you're on Solaris - do a chmod g+s on the directory.

At this point - if the user is a member of the "global" group they can access the workarea. If they are a member of one of the "sub" groups also - they can access the directories for which that sub-group has permissions.

You may need to enable one of the iw.cfg features to ensure that the access rights on the directories are correctly referenced by TS / iwproxy and such - but this is certainly do-able.

chunk

Ghoti,

Maybe it's too early and I need more coffee, but what if you only want the subgroup to be able to write to one subdirectory and not anywhere else?

Example:

group-a needs to be able to write to anywhere except dir-2
group-b needs to be able to write ONLY to dir-2
both groups can read each others' files

Can that be done with a single branch and single/multiple workareas?

Cheers,

chunk

Adam Stoller

Ghoti,

Maybe it's too early and I need more coffee, but what if you only want the subgroup to be able to write to one subdirectory and not anywhere else?

Example:

group-a needs to be able to write to anywhere except dir-2
group-b needs to be able to write ONLY to dir-2
both groups can read each others' files

Can that be done with a single branch and single/multiple workareas?

Cheers,

chunk

The only problem I see here is with the parent directory, but other than that OS permissions should do the trick as far as I can recall.

maddy

hi all,

I have an admin workarea and i want to give access to one of the image folder to a group where they can -
1) create files
2)delete files
3) edit files
4) and all other task that an editor usually do.

Workarea's Teamsite properties:
Sharing : Group
Owner : server\iwadmin
group : server\TS_admin

That image folder has the following teamsite properties:
Owner : server\iwadmin
Group : server\none
Permissions : server\TS_admin:Full Control (All), server\imagegroup: Full Control (All)

Now when the users from the group server\imagegroup went on the image folder under admin workarea ,most of the item from "File" and "edit" menu is grayed out.For instance new folder, edit , etc.

Any ideas to resolve this issues?

I just went thru ur problem and then thought u might be able to help me. I am new to TS and i have this issue where a particular user with only editor rights is not able to view a particular file in a work area and not able to edit it . actually its a maintenance issue so i dont know which approach to follow . can u help?