Defining and managing project roles
Overview
In Blueprint, privileges are defined by certain project administrators at the project role level. Project roles offer you a powerful way to control access to the project. You can use project roles to define various levels of access based on your team or organization's needs. You can then assign users and groups to the appropriate project roles.
Example
John, a senior business analyst, has been asked to create project roles for two different groups of users. The requirements authors require the ability to view, modify, and establish trace relationships. The reviewers of the artifacts only require the ability to view and comment on artifacts.
John creates two new project roles called Authors and Reviewers. He grants the Authors role the following privileges: Read, Edit, and Trace. John grants the Reviewers role the Read and Comment privileges.
Project roles are defined and managed using the Project Roles tab in the Project Administration Console. The Project Roles tab looks like this:
Each role has a name, description, and a set of privileges. The following privileges can be applied to a project role:
| Privilege | Description |
|---|---|
| Read | Provides the ability to view artifacts. |
| Edit | Provides the ability to modify and publish artifacts. If the Edit privilege is granted, the Read privilege is automatically granted. |
| Delete | Provides the ability to delete artifacts. |
| Trace | Provides the ability to create trace relationships between artifacts. If the Trace privilege is granted, the Read privilege is automatically granted. Note: In order to create a trace, the user must also have Edit permissions on at least one of the artifacts. |
| Comment | Provides the ability to add new comments and replies. If the Comment privilege is granted, the Read privilege is automatically granted. |
| Steal Lock |
Provides the ability to steal the lock from other users. If the Steal Lock privilege is granted, the Read and Edit privileges are automatically granted. Warning: Stealing a lock discards all unpublished changes of the user that previously held the lock. |
| Can Report |
Provides the ability to produce Blueprint Analytics reports. If the Can Report privilege is granted, the user can produce Blueprint Analytics reports using the project data in PowerPivot. Note: Blueprint Analytics reporting requires a Blueprint Analytics license. |
| Share via Home Page | Provides the ability to share projects and artifacts to the Home page, allowing all other users with author or collaborate licenses to view the item under Shared Items. |
