Restricting Read access between TeamAreas
I know how to restrict write access to artifacts ( Test Plans, Testcases, ...) to members of other team-areas, but I need to restrict even read access. Is it possible? I tried defining categories in the Project Area, and associating them to team-areas, but, still, as an example, members of each team area can read other team-area Plans.
|
Accepted answer
Currently read-access is only controlled at the Project Area level.
Team Areas can be used for write-access permission. Using Team Areas for read-access is something we've heard before and a valid scenario but not yet implemented in RQM. The enhancement is tracked in Support read access control on team area (74538) Regards, John Nason QM Development sandro de santis selected this answer as the correct answer
|
2 other answers
Paul Slauenwhite (8.4k●1●2)
| answered Jan 13 '14, 9:16 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Jan 15 '14, 8:05 a.m.
Within project areas and team areas, you add users as members. Depending on the access control settings in a project area, membership in that project area or one of its team areas can determine whether a user has access to project area and team area artifacts.
[Source: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.jazz.platform.doc/topics/c_understanding_user_access_control.html] It appears the same users are in both team areas. For more information, see http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.jazz.platform.doc/topics/c_restricting_read_access_project_areas_web.html. Comments Hi Paul,
|
Hi Mark, thank you for your response.
I read the article, and it seems related to Work Items, and using features in RTC. Maybe I am wrong but I did not find anything similar in RQM. Are those features also available in RQM? Thanks |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.