Choosing Role Capabilities

You can assign any number of roles to a single user. This way, users can perform many different roles for multiple project/streams and segments of the product structure.

Additionally, multiple users may share responsibility for a role, even within the same product segment and project/stream. When users share a role on a design part, all users receive email notification and inbox entries when appropriate.

To enforce levels of responsibility, you can assign one of the following capabilities to each user:

- Primary

- Secondary

- Leader

Primary and Secondary

A user with the primary capability has the main responsibility for that role on the design part or object. You can assign this role capability only to a single user.

Primary and leader capabilities are mutually exclusive. If you assign the primary capability to a user, you cannot assign the leader capability to the same user.

Users with the secondary capability act as backup to the user with the primary capability. They have the same privileges as the user with the primary capability.

Leader

An alternative to assigning primary and secondary capabilities is the leader capability. This concept mainly applies to Dimensions CM requests, where a large group of users may need to contribute comments without having the ability to action the request. This does not apply to items.

Leader and primary capabilities are mutually exclusive. If you assign the leader capability to a user, you cannot assign the primary capability to the same user.

By default, users with the leader capability can:

- Update objects.

- Relate and unrelate subordinate objects.

- Add and edit existing action descriptions.

- Action objects to the next lifecycle state.

If you assign the leader capability, the remaining users can only relate/unrelate subordinate objects and add action descriptions.

Related Topics

Managing Roles

Assigning Roles to Baselines

Assigning Roles to Requests

Roles and Lifecycles

Delegating Roles

Special Roles