Project Area member vs. Team Area member permissions

The process permission mechanism is described in article
https://jazz.net/library/article/291
If something in that article is unclear, let us know so we can get it
clarified.
For your particular question, I believe that the process area that is
inspected for permission depends on what team area the new work item is
assigned to. In your case, if the new defect is assigned to the project
area, then it is the project area permissions that would apply (not a
team area's permissions).

Cheers,
Geoff

On 9/23/2011 2:23 PM, zambrano wrote:

Hi, does RTC manage in different ways the permissions for a given role
for a Project Area's member versus a Team Area member?
For example, I defined that a Stakeholder can Create a Defect ( and
Initialize it ), if a stakeholder is a member of the Project Area, it
can do it, but if the stakeholder is a member of a Team Area inside
the Project Area it cannot... as a workaround, if I add permission to
Everybody to Create and Initialize a Defect, then the Team Area's
Stakeholder is able to do it.
Does anybody know why is it happening?