STAGING Security

Aryan

This is regarding handling of confidential content. Consider a hypothetical scenario, where there is a branch with 3 workareas under it. These three workareas are shared by 3 seperate groups. The constraint is that one group cannot view the other's content. This is easily acheived at a workarea level by using the following changes in iw.cfg file.

[iwserver]
branch_security=on
workarea_security=on

But since these workareas share the same STAGING area, one group can VIEW the other's content. How can this be avoided? Is there an out of the box solution in TeamSite, which can restrict one group viewing the other's data even in the STAGING area of the branch?

moonkhanna

This is regarding handling of confidential content. Consider a hypothetical scenario, where there is a branch with 3 workareas under it. These three workareas are shared by 3 seperate groups. The constraint is that one group cannot view the other's content. This is easily acheived at a workarea level by using the following changes in iw.cfg file. [iwserver] branch_security=on workarea_security=on But since these workareas share the same STAGING area, one group can VIEW the other's content. How can this be avoided? Is there an out of the box solution in TeamSite, which can restrict one group viewing the other's data even in the STAGING area of the branch?

Setting appropriate permissions on the files should resolve your issue. also you will need to configure submit.cfg for the permissions..