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

Template Permission issue - TS 6.7.2 SP2, Win2003

Srinivasa Talla

Hi,

We are using TeamSite Groups instead of Windows local Group, which we used in TS 6.5. We added 5 domain users to this group. For each user, the TeamSite is showing the default roles : editor and WorkflowUser. We added this group to workarea. Everything is through program. Sometimes we may add or remove users from the group.

iwaccess set-group workareavpath tsgroupid

So now everyone should have access to this workarea. But when a user(default editor) is trying to edit, TS is giving error like "You don't have permission to edit". There is no issue with Master user.

Is there any setting missing here in TS 6.7.2?

Thanks

Find more posts tagged with

Comments

Adam Stoller

Are you sure you assigned the user (directly or via a group assignment) to a role in the particular branch?

Just because a user (or group) has a role in one branch does not mean that they have that role in other branches.

Also - permissions for templates could be at the file or directory level (e.g.: workarea-root, templatedata/, templatedata/category/, templatedata/category/datatype/, templatedata/.../data/, templatedata/.../presentation/, etc.) - so check those too.

Srinivasa Talla

Thanks ghoti. The user is member of the TeamSite Group(No OS group). We are assuming the following command will set the permission to all items of the workarea (automatic propagation to lower level).

iwaccess set-group WorkareaVPath TSGroupID.

Here we are talking about one particular workarea in a branch.

Do we need to set the group for each file/DCR/template/directory? Is there any difference if we copy files from another place and used the above command to set the group?

Adam Stoller

Thanks ghoti. The user is member of the TeamSite Group(No OS group). We are assuming the following command will set the permission to all items of the workarea (automatic propagation to lower level).

iwaccess set-group WorkareaVPath TSGroupID.

Here we are talking about one particular workarea in a branch.

Do we need to set the group for each file/DCR/template/directory? Is there any difference if we copy files from another place and used the above command to set the group?

You need to check each file and directory - I believe the command you indicated only sets the "group for sharing" on the workarea - and probably does not do anything else.

Srinivasa Talla

Ok. Then we may have 2 ways 1. Is there any command to set at workarea level which automatically applies to all other sub items? 2. Set the group for each item(workarea/directory/file,...). Definitely the 2nd point should work.

Is there any other best way for this?

Crsb

Ok. Then we may have 2 ways 1. Is there any command to set at workarea level which automatically applies to all other sub items? 2. Set the group for each item(workarea/directory/file,...). Definitely the 2nd point should work.

Is there any other best way for this?

Changes in workarea permissions do not transmit to existing files and folders automatically after the change. you will have to use system cmd (chmod in unix/securty tab in windows) and/or TS CTL iwaccess to make global changes to existing directory and its content.
TS file permission issues are usually due to user not having proper role, or wrong file/folder permissions.
Verify that the owner and group of the files and folders are set properly, if you don't want to go thru every file and folder to verify, just reset them using iwaccess. then login to your windows server and set proper owner/group/other permissions in the file system level.

Srinivasa Talla

Each workarea may have more than 200 files/directories, so we have to set all the items with the respective TS group by using a perl script.

The conclusion is "Whenever we copy a work area from another system, we need to set the TS group(it includes the permissions) to workarea and also to all the files/directories in that workarea. There is no single TS command to apply on a workarea which will propagate the group permissions to its all sub items.".

jbonifaci

Each workarea may have more than 200 files/directories, so we have to set all the items with the respective TS group by using a perl script.

The conclusion is "Whenever we copy a work area from another system, we need to set the TS group(it includes the permissions) to workarea and also to all the files/directories in that workarea. There is no single TS command to apply on a workarea which will propagate the group permissions to its all sub items.".

Hmmm, this definitely doesn't sound right. As Adam has already stated, a user needs 2 types of access in order to function fully within a workarea, and it sounds like you're only setting one of them. The user needs a role for the branch (either at the branch level or inherited from a branch higher up the chain) (this is what I think you're missing). They also need access to the workarea (which you're setting via the workarea group for sharing).

And, unless you have changed them to not inherit, all files/folders within the workarea should inherit their permissions from the workarea level by default, so there is no need to recursively set the permissions. (I have noticed this can occasionally take some time to kick in, especially if you have groups within groups).

So the first thing I would check is that your users have roles within the branch your workarea resides (not just access to the workarea).

~Jeff