Member Role inheritance in subteams
One part of the web client for adding members to a subteam says:
"The roles assignments below are also valid in all child team areas." This seems to imply that when creating a subteam, the roles will be inherited from the parent(s).
But another part (when the new members for a new subteam are saved) says something like No roles were assigned when adding members - they will only have "default" access. This goes on to recommend adding roles.
If the member roles are not changing in the subteam, can I leave this specification blank in the subteam member list, and "inherit" the setting from the parent team for that member? If that member is not a member of the parent team, but is a member of some higher up "parent", does he/she inherit from the first match found going up the hierarchy?
"The roles assignments below are also valid in all child team areas." This seems to imply that when creating a subteam, the roles will be inherited from the parent(s).
But another part (when the new members for a new subteam are saved) says something like No roles were assigned when adding members - they will only have "default" access. This goes on to recommend adding roles.
If the member roles are not changing in the subteam, can I leave this specification blank in the subteam member list, and "inherit" the setting from the parent team for that member? If that member is not a member of the parent team, but is a member of some higher up "parent", does he/she inherit from the first match found going up the hierarchy?
Accepted answer
On 3/14/12 10:41 , marshallschor wrote:
Yes. Role assignments are essentially inherited by subteams. (See my
response to your other post for more details.)
When checking permissions, a user inherits all roles from all parent
teams areas all the way up the hierarchy, not just from the first parent
team area where the user has an assigned role.
For example, if user A is a member of the project area with the role
Observer, is a member of a top-level team with the role Team Member, and
is a member of a subteam with the role Team Lead, and if user A performs
an operation in the context of the subteam, then RTC will check the
permissions for the roles Team Lead, Team Member, and Observer, in that
order.
If a user is assigned a role in the project area or in a parent team
area, there is no way to completely revoke that role in a subteam. (But
you can specify the permissions for that role in the subteam in a way
that effectively revokes the things that role can perform if the
operation were happening in a parent team area.)
--
David Olsen | IBM Rational | Jazz Process Team
If the member roles are not changing in the subteam, can I leave this
specification blank in the subteam member list, and
"inherit" the setting from the parent team for that member?
Yes. Role assignments are essentially inherited by subteams. (See my
response to your other post for more details.)
If that member is not a member of the parent team, but is a member of
some higher up "parent", does he/she inherit from the first
match found going up the hierarchy?
When checking permissions, a user inherits all roles from all parent
teams areas all the way up the hierarchy, not just from the first parent
team area where the user has an assigned role.
For example, if user A is a member of the project area with the role
Observer, is a member of a top-level team with the role Team Member, and
is a member of a subteam with the role Team Lead, and if user A performs
an operation in the context of the subteam, then RTC will check the
permissions for the roles Team Lead, Team Member, and Observer, in that
order.
If a user is assigned a role in the project area or in a parent team
area, there is no way to completely revoke that role in a subteam. (But
you can specify the permissions for that role in the subteam in a way
that effectively revokes the things that role can perform if the
operation were happening in a parent team area.)
--
David Olsen | IBM Rational | Jazz Process Team
