Restricting access to source code and update fields
One of the teams we support wants to use RTC but needs to understand more about restricting access to source code, team additions and work item field updates. Can you tell me whether:
1. You can restrict teams from even viewing source code and if so how?
2. It is possible to restrict which users can add new users to a team area?
3. It is possible to restrict who can assign roles to a team member. For example, to only allow a user to assign a role to a member of their team if they too have that role or better?
3. Users can be prevented from updating certain fields in work items based (say) upon their role?
1. You can restrict teams from even viewing source code and if so how?
2. It is possible to restrict which users can add new users to a team area?
3. It is possible to restrict who can assign roles to a team member. For example, to only allow a user to assign a role to a member of their team if they too have that role or better?
3. Users can be prevented from updating certain fields in work items based (say) upon their role?
One answer
Hi,
1. You can restrict teams from even viewing source code and if so how?
In 3.x versions (not sure which) streams and components can have an owner the visibility can be restricted to the owner e.g. a team. This is done on the stream editor.
2. It is possible to restrict which users can add new users to a team area?
This is part of the process configuration options and can be found in the permissions for the project area and the team area. E.g. who can save a project area or who can modify a team area (add users etc). This is done by role. In addition admin users of the project area and users with repository permission JazzProjectAdmins and JazzAdmins can do certain tasks e.g. give roles these permissions and then do it.
3. It is possible to restrict who can assign roles to a team member. For example, to only allow a user to assign a role to a member of their team if they too have that role or better?
I believe the same as above applies but is not that fine grained. If the user has no right to modify a project area he has no right. there is no permission I am aware off that restricts who can modify which roles.
In addition you probably want someone in charge of doing that, who knows what he is doing anyway.
3. Users can be prevented from updating certain fields in work items based (say) upon their role?
This is in the same spot and by role.
1. You can restrict teams from even viewing source code and if so how?
In 3.x versions (not sure which) streams and components can have an owner the visibility can be restricted to the owner e.g. a team. This is done on the stream editor.
2. It is possible to restrict which users can add new users to a team area?
This is part of the process configuration options and can be found in the permissions for the project area and the team area. E.g. who can save a project area or who can modify a team area (add users etc). This is done by role. In addition admin users of the project area and users with repository permission JazzProjectAdmins and JazzAdmins can do certain tasks e.g. give roles these permissions and then do it.
3. It is possible to restrict who can assign roles to a team member. For example, to only allow a user to assign a role to a member of their team if they too have that role or better?
I believe the same as above applies but is not that fine grained. If the user has no right to modify a project area he has no right. there is no permission I am aware off that restricts who can modify which roles.
In addition you probably want someone in charge of doing that, who knows what he is doing anyway.
3. Users can be prevented from updating certain fields in work items based (say) upon their role?
This is in the same spot and by role.