We encountered the following permission issue when one user with contributor role in a project area tried to create a team area or add one user to the members of an existing team area:
No permission to save Team Area (Server)

We checked the process configuration in the project area. For contributor role, all permitted actions are checked under Save Team Area (server) with Permissions under Team Configuration.


Under Project Cofiguration, for the Permission, we unchecked Modify the process configuration, Modify the collection of process attachments, Modify the collection of team members. But we do have Modify the project area properties and Modify the iteration structure checked.

So it looks like the configuration at project cofiguration overwrite one in Team Configuration for the permission, given the fact that the user can't add new member to an existing team area, whih assumingly caused by unchecking Modify the collection of team members in project area permission.


Is this expected behaviour or we are missing something here?

We want to have fine-grained permisssion control to avoid teamlead role in project area from changing process configuration we want to keep consistent across all project areas and teams.

We can solve this issue by give the user teamlead role in project area but thta is what we try not to do.

Any thoughts?