Managing licenses
Overview
A user's effective access in Blueprint is the intersection of their
Examples
If William has a collaborator license, he is not able to edit requirements even if a project role assignment grants him Edit privileges. William needs an author license to utilize the Edit privileges that are set in the project role assignment. In other words, licenses can limit/override the privileges outlined in a project role assignment to ensure that licenses are enforced.
If Brenda has an author license, she is not able to edit requirements if a project role assignment only grants her Read and Comment privileges. In this case, the project role assignment permissions are respected and Brenda is limited to reading and commenting on artifacts even though she has an author license. In other words, the license assignment does not automatically grant access to users in the absence of a project role assignment.
There are three types of Blueprint licenses:
-
Author: An author license allows users to author requirements in Blueprint, as well as perform all of the tasks that a user with a collaborate license can perform.
- Collaborator: A collaborate license allows users to login to Blueprint to perform tasks such as simulating use cases and participating in reviews.
- View: A view license only allows users to access a single artifact accessed by the artifact URL. The user can view the artifact properties, comments, traces, and historical information. You cannot create a view license group because the view license is the default license type.
Maximum capabilities by license type
Important: Project role assignments are used to grant privileges to users so they can access artifacts in Blueprint. Licenses simply enforce a maximum capability level.
| Capability | Author License | Collaborate License | View License |
|---|---|---|---|
| View single requirement via URL |
|
|
|
| Browse and view requirements |
|
|
|
| Create and participate in discussions |
|
|
|
| Participate in requirements reviews |
|
|
|
| Simulate requirements |
|
|
|
| Setup and manage requirements reviews |
|
||
| Create and edit requirements |
|
||
| Create and edit projects |
|
||
| Generate documents and import/export |
|
||
| Push requirements to ALM systems |
|
