What tasks can only be done by project area administrators?
A group is working on a cloud deployment of CLM and is trying to automate most of the project administration (project creation, user creation, role assignment, etc.) and restrict certain tasks by the project owner.
1. What actions canonly be done by a project area administrator, but cannot be done by any role defined within the process? For example:
- Modify the process configuration?
- Change project configuration data?
- Create roles?
- Define work item categories?
Or in other words, if the "project owner" was not specified as the "administrator" of the project, but was rather given a fairly all-encompassing role, what could he/she not do?
2. Can the permissions of the project area administrator be changed or limited? For example:
- Disallow the creation of new roles
- Disallow the creation of new work item types
Any pointers or answers are greatly appreciated.
1. What actions can
- Modify the process configuration?
- Change project configuration data?
- Create roles?
- Define work item categories?
Or in other words, if the "project owner" was not specified as the "administrator" of the project, but was rather given a fairly all-encompassing role, what could he/she not do?
2. Can the permissions of the project area administrator be changed or limited? For example:
- Disallow the creation of new roles
- Disallow the creation of new work item types
Any pointers or answers are greatly appreciated.
Accepted answer
1. There is nothing that can be done by an administrator of a project area that can not be done with a role and appropriate permissions by a member of the project area. Administrators of the project area are only allowed 1 exemption to the normal process operation enforcement rules. They are allowed to modify the project area itself. They are implicitly granted permission to execute the "Save Project Area" operation that can be configured for any member of the project area. They however wouldn't be able to perform any other operation unless they were a member with the appropriate role that grants the permission. You can see when this exemption is in operation because the team advisor will include a message when the "Save Project Area" operation is run that indicates it was allowed due to an administrative override.
2. Generally no..the granularity is at the "Save Project Area" operation level. There are currently no other operations for administrators or members for that matter that would allow only certain attributes of the project area itself to be changed. The two examples you site are both within the project area data itself so they are governed by the above operation. There may be other attributes on contributed tabs by others however that are governed by other operations that would not be included as part of the administrative override and would need a role with the appropriate permissions to execute successfully.
2. Generally no..the granularity is at the "Save Project Area" operation level. There are currently no other operations for administrators or members for that matter that would allow only certain attributes of the project area itself to be changed. The two examples you site are both within the project area data itself so they are governed by the above operation. There may be other attributes on contributed tabs by others however that are governed by other operations that would not be included as part of the administrative override and would need a role with the appropriate permissions to execute successfully.
One other answer
It is my understanding that the ability to modify the work allocations
of other members of the project is an ability that only the
administrator of a project has, and that there is no role-based
permission that can be assigned that will give a member of the project
area this ability.
Cheers,
Geoff
On 2/8/2012 11:38 AM, dmweinan wrote:
of other members of the project is an ability that only the
administrator of a project has, and that there is no role-based
permission that can be assigned that will give a member of the project
area this ability.
Cheers,
Geoff
On 2/8/2012 11:38 AM, dmweinan wrote:
1. There is nothing that can be done by an administrator of a project
area that can not be done with a role and appropriate permissions by
a member of the project area. Administrators of the project area
are only allowed 1 exemption to the normal process operation
enforcement rules. They are allowed to modify the project area
itself. They are implicitly granted permission to execute the
"Save Project Area" operation that can be configured for
any member of the project area. They however wouldn't be able to
perform any other operation unless they were a member with the
appropriate role that grants the permission. You can see when this
exemption is in operation because the team advisor will include a
message when the "Save Project Area" operation is run that
indicates it was allowed due to an administrative override.
2. Generally no..the granularity is at the "Save Project
Area" operation level. There are currently no other operations
for administrators or members for that matter that would allow only
certain attributes of the project area itself to be changed. The two
examples you site are both within the project area data itself so they
are governed by the above operation. There may be other attributes on
contributed tabs by others however that are governed by other
operations that would not be included as part of the administrative
override and would need a role with the appropriate permissions to
execute successfully.
Comments
Your understanding is kind of correct. First the currently shipping product does not allow that. There has been some work in 4.0 to enable it and potentially backport it to 3.0.1.x. Second, work allocations are primarily associated to the user not a project area so the user editor was governing it like all other user attributes. Planning put in in their own "administrative override" feature which in my opinion is wrong and I've voiced that in the relevant workitem. It should be a process enabled operation in my opinion like everything else.
Regards,
Don
Jazz Process Component Lead
It is my understanding that the ability to modify the work allocations
of other members of the project is an ability that only the
administrator of a project has, and that there is no role-based
permission that can be assigned that will give a member of the project
area this ability.
Cheers,
Geoff
On 2/8/2012 11:38 AM, dmweinan wrote:
1. There is nothing that can be done by an administrator of a project
area that can not be done with a role and appropriate permissions by
a member of the project area. Administrators of the project area
are only allowed 1 exemption to the normal process operation
enforcement rules. They are allowed to modify the project area
itself. They are implicitly granted permission to execute the
"Save Project Area" operation that can be configured for
any member of the project area. They however wouldn't be able to
perform any other operation unless they were a member with the
appropriate role that grants the permission. You can see when this
exemption is in operation because the team advisor will include a
message when the "Save Project Area" operation is run that
indicates it was allowed due to an administrative override.
2. Generally no..the granularity is at the "Save Project
Area" operation level. There are currently no other operations
for administrators or members for that matter that would allow only
certain attributes of the project area itself to be changed. The two
examples you site are both within the project area data itself so they
are governed by the above operation. There may be other attributes on
contributed tabs by others however that are governed by other
operations that would not be included as part of the administrative
override and would need a role with the appropriate permissions to
execute successfully.