restricting access to particular teams to particular streams
Pavitra Chitikela (15●2●12)
| asked Jun 28 '17, 2:06 a.m.
retagged Jul 02 '17, 11:37 a.m. by Ken Tessier (841●1●7) Hi, I have 3 streams in my project area: DEV, Release, and Continuous. I created different teams to access these streams. “Developer Team, “R Release developer” team and “Continuation developer” team. <o:p> </o:p> 1) Now my problem is that “Continuation developer” team is able to load stream of “R Release developer”.I don't want release streams to be visible to other team members. Can anyone suggest what’s the best way to restrict the access to streams so that only users with an appropriate role can load the streams and make changes 2) Only one stream in release stream is not visible to “Continuation developer” team. All other release streams are visible to them. We are not knowing the reason for this behavior. Please suggest the best way to implement this type of configuration. Regards, Pavitra |
Accepted answer
Hi Pavitra,
Pavitra Chitikela selected this answer as the correct answer
Comments
Pavitra Chitikela
commented Jun 28 '17, 5:30 a.m.
Hi Arun, The solution you have given is working. Thanks for the update. Regards, Pavitra
Pavitra Chitikela
commented Jun 29 '17, 5:31 a.m.
Hi Arun,
Geoffrey Clemm
commented Jul 22 '17, 2:17 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
(1) The owner of a repository workspace can always access that workspace. Why do you care whether they can load that workspace?
(2) Creating a repository workspace on a stream does not give you permission to modify that stream. Use write access control (permissions and preconditions) on the stream to control who can modify it.
|
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.