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 Groups

System

Hello,

I have some issues with the newsy introduced TeamSite groups, running TS6.5 on Windows Server 2003.

Scenario:

I have one local OS group: "marketGroup" which is included in a TS group called "CompanyUsers"
The OS group contains one user: "tsauthor"

In my submit.cfg I have set up rules stating that everything below /templatedata/.*/.*/data/market will be assigned to the "marketGroup".
Next rule in submit.cfg assigns every file to the TS group "CompanyUsers".

These rules are ok (checked with iwtestcfg), and also the result when browsing through teamsite (as master) seems ok.

Now, when logging in as the tsauthor user (which is a member of "marketGroup", and thereby also included in "CompanyUsers", I can only access the files below "/templatedata/.*/.*/data/market". Checking the other files (for example in workarea root) says "Owner: administrator", "Group: CompanyUsers" and "Permissions iwglobal:Read(RX)".

According to the "TeamSite 6.1 VS TeamSite 6.5" thread, I reccon that these settings are ok - still, the files are not accessible for "tsauthor".
Am I missing something here? could anyone point me in any direction?

Kind regards
# Martin

Find more posts tagged with

Comments

smenon

If you view file properties from the UI - what does it display for permissions? And who is the owner of the workarea and what is the group for sharing for the workarea?

--Sunil Menon
Product Manager
Interwoven, Inc.

cascade.rptdesign

Migrateduser

Thank you for your reply,

the file properties (for files that tsauthor can not access) in the UI is the ones that i described in my intital post: "Owner: administrator", "Group: CompanyUsers" and "Permissions iwglobal:Read(RX)".

Accessible files have owner: administrator, group: domain\marketGroup, permissions: domain\marketGroup: Add & Read (RWX).

Checking the properties of the workarea it says: sharing: group, owner: domain\Administrator, group: CompanyUsers (which is the TS group)

Any ideas?

Thank you!
# Martin

Adam Stoller

If the marketGroup user(s) does not have access to the directories leading upto the directory where you've granted them access - they may not be able to get there.

Are you sure your second rule for assigning all files to CompanyUsers is only operating on files - and not directories?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

The directory permissions is ok, and even files that are in workarea root are not possible to access.

Reading on in the TS manual, I found this:

TeamSite also provides managed groups and group membership (referred to as TeamSite
groups) to complement the OS groups that TeamSite uses as groups for sharing branches and
workareas.

Could it be that TS groups only applies to branch- and workarea level and can not be set as the group for a specific file/directory?

# Martin

Adam Stoller

I don't know - haven't played with 6.5 yet.
You should probably contact Support and get them to work with you to determine the source of the problem

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

13adam13

The documentation seems to imply that you are correct. TS Groups are only to augment the "group for Sharing" capabilities of the branches and workareas.

Please update this post with any feedback from Interwoven on this one, as the documentation does seem a bit fuzzy.

--Adam Wilson
Senior Programmer

Dwayne

See this thread for a discussion on this topic.

--

Current project: TS 5.5.2/6.1 W2K

smenon

TeamSite Groups is applicable to all assets and not just branches or workareas. You should be able to use TeamSite Groups interchangeably with OS Groups for any feature in TeamSite where you used groups - branch/workarea creation, file permissions, submit.cfg, workflow group tasks etc

If you are having trouble please contact Support and open a case for this issue.

--Sunil Menon
Product Manager
Interwoven, Inc.

Migrateduser

Thank you all for your replies,

yes, when using iwchgrp directly on the assets it works fine - so... back to basics and check the submit.cfg file again - as fish correctly suspected

Thanks

# martin