Team Permissions vs Project Permissions
Whilst looking at the project permissions per role I drilled down to the Team permissions and expected to see the role permissions inherited from Project to Team. However I find that the tick boxes per role within the team are not auto-filled from the Project.
I then notice that you can access the Team permissions in two ways. Firstly by going into the Team from the Web UI and through the Project and clicking on the Team name on the right hand side then click on Permissions. This way the permissions per role are not in-herited or auto-filled. In the Project in the Web UI and select Permissions > Team Configuration > Developer I see that the role permissions are auto-filled. Why are there two ways of assigning permissions to the teams roles? Why is one way auto-filled with the role permissions and the other isn't? Are they separate team permissions? Thanks Sally & Gwen :D |
2 answers
|
Team areas will inherit the settings of the Team Configuration permissions
from their parent project area. When you configure the Team Configuration Permissions within a project area editor (the second of your two ways), this configuration will be used as the default process for any team area within the hierarchy. Then in the team area editor (the first of your two ways), each team area can also configure the permissions even overriding the inherited permissions from the project area or a parent team area (if they are not marked final). The inherited permissions are not displayed within the trees of the editors. More details can be found here: https://jazz.net/wiki/bin/view/Main/ProcessConfiguration HTH Darin Jazz Process Team "sallyanne" <sallyanne> wrote in message news:hcv564$udp$1@localhost.localdomain... Whilst looking at the project permissions per role I drilled down to |
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.