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 User Permissions Error

ntaylor

Hi All,

I set up a new user in TeamSite mirroring all the same settings as another user (Permissions, groups, etc.) The issue is that this new user cannot even edit pages in TeamSite although his permissions say otherwise. He is part of an "EditorGroup" which has page editing privileges. I checked to make sure that the groups were writing correctly to tsgroups.xml and then were.

The logs show that no errors occured when adding him to the group.

Does anyone have any ideas about what might be causing this?

Using TeamSite 6.7.2 on Solaris 10.

Find more posts tagged with

Comments

Migrateduser

- Did you check the owner, group, permission of the page; which the new user is trying to edit?

- Also can the new user create file/folder in the workarea?

Adam Stoller

Hi All,

I set up a new user in TeamSite mirroring all the same settings as another user (Permissions, groups, etc.) The issue is that this new user cannot even edit pages in TeamSite although his permissions say otherwise. He is part of an "EditorGroup" which has page editing privileges. I checked to make sure that the groups were writing correctly to tsgroups.xml and then were.

The logs show that no errors occured when adding him to the group.

Does anyone have any ideas about what might be causing this?

Using TeamSite 6.7.2 on Solaris 10.

Did you run iwreset after adding the user or wait up to 10 minutes before attempting to do anything with this user account within TeamSite? If not, you might just be hitting a caching / timing issue.

Firenze

Did you make sure user was added to the branch or parent branch? Unless user is a master, the user won't be able to edit files without a role.

ntaylor

Thanks restarting the server brought up everything correctly.

One other question though, the templatedata directory has different group permissions than the site idirectory tself. These should be the same (templatedata), but when I change the templatedata folder to match the permissions of the site, it gets changed back somehow. Any ideas on what may be causing this?

Thanks.

Firenze

If you can elaborate on how you are changing permissions, it would be helpful.

Here are some nuances I have observed on how permission changes may get confusing.

1. Directory permissions do not get affected by submit.cfg if the directory has already been submitted once.
2. If you are using the Properties screen and manually changing the permission of a group on a folder and you don't Tab out of that field and then click Save, the change is not recorded.

ntaylor

The entire branch should be set as one group permission called EditorGroup. For some reason the templatedata directory is different and is not included in this. Changing the permissions by clicking properties/permissions works for some time but then is reset back to its original state, not allowing EditorGroup to use it.

Firenze

Do you have a setting in iw.cfg for
mask_workarea_access

Have you tried creating another branch or another workarea to see if the problem is consistent?

ntaylor

No, I do not have a setting in iw.cfg for mask_workarea_access. It appears to edit permissions on the folders when I submit files from the ReleaseZone to their respective folders outside of the ReleaseZone. Also, I have tried creating another workarea and the problem is not consistent. It only seems to happen in the templatedata directory under one site.

ntaylor

Thanks for all the help. The problem was solved and had to do with our custom workflows and the way submit.cfg was configured.