When more than one user has the same role, you can assign a role capability to determine different levels of responsibility within those users. The role capabilities that can be assigned to the users within the role are Leader, Primary, or Secondary, described below:
Leader: It is sometimes useful to have more than one user with a particular role with respect to an item-spec or request e.g. so that they can add comments (called Action Descriptions in requests). However, it may also be appropriate to restrict the number of users in this group who can actually action the object to the next stage in its lifecycle. The way to implement this is via the Leader function. When the Leader capability is defined in a group of users who have the same role for a given object, only the Leader can update the associated attributes and action on the object. All other users with that role may add only Action Descriptions or user comments. If the Leader role capability is assigned to a user, then the Primary role capability (described below) cannot be assigned to the same user i.e. Leader role and Primary role capabilities are mutually exclusive.
Primary: The Primary capability for a role in the lifecycle of an object is assigned to the user regarded in the project as having the main responsibility for that role on the object. There cannot be more than one Primary user defined for a role (as applicable to any particular design part or segment of the product structure). If the Primary role function is assigned to a user, then Leader role capability (described above) cannot be assigned to the same user.
Secondary: Secondary users are intended to act as deputies for the Primary. They have exactly the same privileges as the Primary: they can add action comments and also, unless the Leader capability has been assigned, update the object's attributes and action it.