Question about RTC 3.0.1 privilege setting
2 answers
Hi,
we are trying to make understand the RTC 3.0.1 privilege setting, one question we have now is, user belong to team A can deliver change to a stream owned by team B which is a child team of A, is this normal? how is it working? we can't find much information about this.
Regards,
Makson
Hi Makson,
an article that sheds some light on this is https://jazz.net/library/article/292 which also mentions the article https://jazz.net/library/article/291 . Although both articles are for RTC2.0 there are no significant changes except additional read access and ownership options for components, streams etc.
Doing that from my memory: It comes down to inheritance of membership for project, teams, roles assigned and permissions for general roles such as everyone.
In your case since team B is a child team of team A the user of team A inherits its role from team A and if that role in Team B has permission to deliver to streams owned by team B.
If the teams would be not in a parent child relationship the team member of team A would not inherit that role in team B, unless he has it on an even higher level. The user would potentially have the role "Everyone" and the permissions for that role on team B would determine if or if not he can deliver.
Hi Ralph,
thanks, that's a really useful information.
Regards,
Makson
Hi Makson,
an article that sheds some light on this is https://jazz.net/library/article/292 which also mentions the article https://jazz.net/library/article/291 . Although both articles are for RTC2.0 there are no significant changes except additional read access and ownership options for components, streams etc.
Doing that from my memory: It comes down to inheritance of membership for project, teams, roles assigned and permissions for general roles such as everyone.
In your case since team B is a child team of team A the user of team A inherits its role from team A and if that role in Team B has permission to deliver to streams owned by team B.
If the teams would be not in a parent child relationship the team member of team A would not inherit that role in team B, unless he has it on an even higher level. The user would potentially have the role "Everyone" and the permissions for that role on team B would determine if or if not he can deliver.
thanks, that's a really useful information.
Regards,
Makson
Hi,
we are trying to make understand the RTC 3.0.1 privilege setting, one question we have now is, user belong to team A can deliver change to a stream owned by team B which is a child team of A, is this normal? how is it working? we can't find much information about this.
Regards,
Makson
Hi Makson,
an article that sheds some light on this is https://jazz.net/library/article/292 which also mentions the article https://jazz.net/library/article/291 . Although both articles are for RTC2.0 there are no significant changes except additional read access and ownership options for components, streams etc.
Doing that from my memory: It comes down to inheritance of membership for project, teams, roles assigned and permissions for general roles such as everyone.
In your case since team B is a child team of team A the user of team A inherits its role from team A and if that role in Team B has permission to deliver to streams owned by team B.
If the teams would be not in a parent child relationship the team member of team A would not inherit that role in team B, unless he has it on an even higher level. The user would potentially have the role "Everyone" and the permissions for that role on team B would determine if or if not he can deliver.