Separate RTC permission inheritance trees for admin/role property?
Hi,
Accepted answer
Marko,
this is how this works: https://jazz.net/library/article/291 for all I know.
As far as I can tell, being Administrator on a project area (vs having the JazzAdmin repository role) only allows you to give yourself (and others) roles and permissions in that PA.
Comments
Hi Ralph,
Administrator is not a role for all I know.
As I said, the users listed as administrator in the process area only have the ability to give themselves roles and permissions and save the project areas process, even if they don't have roles and permissions that would allow this initially. This can be seen in the process advisor and is called "Administrator Override" as far as I remember.
After reading this article https://jazz.net//library/article/292 I think I got it now. Thanks for pointing me to the right article and forcing me to understand it by myself :)
It is quite complex. I struggle as well.
One other answer
To summarize, "Administrators" is not a role, but is inherited by child team areas.
Comments
But what about this statement on the web ui: Team administrators can modify and save this team area and its child team areas.
Oops. I put an extra "not" in my answer (now corrected :-).
Even if you are member of the administrators group you have to provide yourself with a role and the role with permissions in order to do anything other than
- Creating, assigning roles and permissions to role
- Saving the process area process
So it is more that it allows to take the role and permission needed.
Or another way to express the difference is that what an Administrator can do is hard-wired and cannot be modified, while the permissions assigned to actual roles can be specified (if you have the appropriate permissions :-).