For a complete description of how process permissions are determined,
please see: https://jazz.net/library/article/291

To summarize:
First, it determines what process area "governs" the object being
modified (commonly, the process area that "owns" that object).
Then it determines what roles you have in that process area. You have a
permission if any of your roles has that permission.

So in your case, the first thing that matters is what process area are
you trying to create the build engine in. Let's suppose you are trying
to create it in the project area (and not one of the team areas). In
that case, what matters is what roles you are given in the project area.
It wouldn't matter what roles you had in any of the team areas ... all
that matters is whether or not any of your roles in the project area has
permission to create build engines. If you have been given no explicit
roles in the project area, then you only have the default "Everyone" role.

So if members of a child team area can create build engines, but members
of a grandchild team area cannot, then something else must be going on
(or there is a bug). In particular, check what process area you are
trying to create the build engine in. Then check whether the team
members who are able to create build engines have been given an explicit
role in the project area.

Cheers,
Geoff

On 1/6/2012 11:53 AM, carrouss wrote:

Hi

I have the following set up - a project area where team member has
permission to create a build engine. I have a sub team, which
inherits the process of the project area - I have not modified this
at all. Team members of this team can successfully create a build
engine. I then have a sub team underneath this team, again, this
inherits from it's parent. A team member in this team can NOT create
a build engine.

I believe it should. Am I right?

For a complete description of how process permissions are determined,
please see: https://jazz.net/library/article/291

To summarize:
First, it determines what process area "governs" the object being
modified (commonly, the process area that "owns" that object).
Then it determines what roles you have in that process area. You have a
permission if any of your roles has that permission.

So in your case, the first thing that matters is what process area are
you trying to create the build engine in. Let's suppose you are trying
to create it in the project area (and not one of the team areas). In
that case, what matters is what roles you are given in the project area.
It wouldn't matter what roles you had in any of the team areas ... all
that matters is whether or not any of your roles in the project area has
permission to create build engines. If you have been given no explicit
roles in the project area, then you only have the default "Everyone" role.

So if members of a child team area can create build engines, but members
of a grandchild team area cannot, then something else must be going on
(or there is a bug). In particular, check what process area you are
trying to create the build engine in. Then check whether the team
members who are able to create build engines have been given an explicit
role in the project area.

Cheers,
Geoff

On 1/6/2012 11:53 AM, carrouss wrote:

Hi

I have the following set up - a project area where team member has
permission to create a build engine. I have a sub team, which
inherits the process of the project area - I have not modified this
at all. Team members of this team can successfully create a build
engine. I then have a sub team underneath this team, again, this
inherits from it's parent. A team member in this team can NOT create
a build engine.

I believe it should. Am I right?

I have a similar situation - however we do not have any people registered at the PA level only at teams - as the person doesn't exist in the PA there are no inheritance of values ... in 2.0x version I could be at the team level only and get the correct team permissions .. are we now saying that I have to be at the PA level as well as the team level in order for the inheritance to work ... this doesn't seem right

Inheritance is through any sub-team relationships ... i.e. starting at
the project area, down to the sub-teams of that project area, and down
to the sub-teams of those teams, transitively.

The inheritance from the project area to its immediate child team areas
was just mentioned as an example.

Cheers,
Geoff

On 1/23/2012 3:53 PM, nerack wrote:

gmclemmwrote:
For a complete description of how process permissions are determined,

please see: https://jazz.net/library/article/291

To summarize:
First, it determines what process area "governs" the
object being
modified (commonly, the process area that "owns" that
object).
Then it determines what roles you have in that process area. You
have a
permission if any of your roles has that permission.

So in your case, the first thing that matters is what process area
are
you trying to create the build engine in. Let's suppose you are
trying
to create it in the project area (and not one of the team areas).
In
that case, what matters is what roles you are given in the project
area.
It wouldn't matter what roles you had in any of the team areas ...
all
that matters is whether or not any of your roles in the project area
has
permission to create build engines. If you have been given no
explicit
roles in the project area, then you only have the default
"Everyone" role.

So if members of a child team area can create build engines, but
members
of a grandchild team area cannot, then something else must be going
on
(or there is a bug). In particular, check what process area you are

trying to create the build engine in. Then check whether the team
members who are able to create build engines have been given an
explicit
role in the project area.

Cheers,
Geoff

On 1/6/2012 11:53 AM, carrouss wrote:
Hi

I have the following set up - a project area where team member has
permission to create a build engine. I have a sub team, which
inherits the process of the project area - I have not modified this
at all. Team members of this team can successfully create a build
engine. I then have a sub team underneath this team, again, this
inherits from it's parent. A team member in this team can NOT
create
a build engine.

I believe it should. Am I right?

I have a similar situation - however we do not have any people
registered at the PA level only at teams - as the person doesn't
exist in the PA there are no inheritance of values ... in 2.0x
version I could be at the team level only and get the correct team
permissions .. are we now saying that I have to be at the PA level as
well as the team level in order for the inheritance to work ... this
doesn't seem right