Roles

Roles identify the functions of team members. Permissions for specific operations can be assigned to roles at the project level or within a team area. The default role permissions apply to all users in the repository. Each project area can define a set of roles in the project's process configuration, and the roles can be edited in the process configuration interface. Teams can also add their own roles in their team area customization.

You can assign one or more roles to a user in the Edit Process Roles window. The order of a user's assigned roles reflects their relative priority. When behavior is configured for multiple roles, the process executes the behavior associated with the user's highest-priority role. Priority does not affect permissions; users can perform actions granted through any of their assigned roles.

The graphic shows the Edit Process Roles window with the contributor role selected.

There is a predefined role named default. The default role cannot be assigned, removed, or reordered. All users in the repository assume the default role. Team members are assigned the default role and any other roles that are explicitly assigned when they are added to a team.

Roles are defined on the Process Configuration tab or the Process Configuration Source tab of the Project Area editor or Process Template editor. These roles apply to the entire project. To modify roles for a team area, use the Process Customization tab or Process Customization Source tab of the Team Area editor.

The roles definition includes an identifier, name, description, and a cardinality value, which controls whether the role can be assigned to more than one user in the project area or team area.


Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug