RRC - Folder Security
we are on RRC 4.0 on a windows 2008R2 server with Websphere and backend SQL database v2008R2
We created two team areas with one user in each team area. We created two artifact folders and assigned each folder one of the above team area. We discovered that a user from one team area can create/edit/delete artifacts from the other team area's folder even though their team area is not allowed...
Is this a defect or did we miss something in the setup?
Thanks
One answer
What role in the project area do the members of the team have?
I ask because the role defined in the project area is project wide and supersedes the role defined in a team area. For example if somebody has Author role at the project level, then they still have author role even if the team area membership has them as commentor role.
So typically what we do is give team leads (and project admins) author role at the project level so they can always author content but then the other members are given the default role which is typically commentor and then for each team area they are given explicit author access, so they can only author content in those assign folders. With the default Commentor role you can always comment and link any artifacts in the project.
Now if they don't explicitly have author rights at the project level, then check to see what permissions are set for the default role.
If everything is correct then I would suggest contacting tech support for further investigation because this does not sound right.
I ask because the role defined in the project area is project wide and supersedes the role defined in a team area. For example if somebody has Author role at the project level, then they still have author role even if the team area membership has them as commentor role.
So typically what we do is give team leads (and project admins) author role at the project level so they can always author content but then the other members are given the default role which is typically commentor and then for each team area they are given explicit author access, so they can only author content in those assign folders. With the default Commentor role you can always comment and link any artifacts in the project.
Now if they don't explicitly have author rights at the project level, then check to see what permissions are set for the default role.
If everything is correct then I would suggest contacting tech support for further investigation because this does not sound right.