Managing licenses
Overview
From a licensing perspective, Blueprint users are known as Authors, and have universal capabilities. An individual user's privileges within a given project are determined by their Project-role assignments.
About legacy licensing
In Blueprint deployments that use a legacy licensing model, there is also a Collaborate license type that has different capabilities:
- 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.
- Collaborator: A Collaborate license allows users to login to Blueprint to perform tasks such as simulating use cases and participating in reviews.
-
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.
Maximum capabilities by license type
| 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 |
|
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.
Example
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.
