Lifecycle management roles and permissions
This topic lists the global and resource permissions required to carry out tasks related to Lifecycle management. Some actions require a combination of a global permission and a resource permission.
Global permissions
| Global permission | Description | Required license | New license |
|---|---|---|---|
| Product Rights > AI Governance | Required to access Lifecycle management for AI-related asset types in AI Command Center. | Read-only | Viewer |
| Product Rights > Assessments | Allows users to access Assessments. They can view public assessments and the assessments that they own or are assigned. | Read-only | Contributor |
| Assessments > Conduct Assessments | Allows users to conduct, edit, copy, delete, and make assessments obsolete. Required to add assessments to the Lifecycle tracker using the Start button. Without this permission, the Start button is not shown. | Standard | Contributor |
Resource permissions
The following resource permissions apply to the community or domain in which the asset is stored.
| Resource permission | Description | Required license | New license |
|---|---|---|---|
| Asset > Lifecycle Management > Assessment | Allows users to add assessments to the Lifecycle tracker. Can be used as an alternative to the Assessments > Conduct Assessments global permission. | Standard | Creator |
| Asset > Lifecycle Management > Decision Record |
Note Decision record activities no longer exist. |
Standard | Creator |
| Asset > Lifecycle Management > Sign-Off | Allows users to add sign-off activities to the Lifecycle tracker. | Standard | Creator |
| Asset > Lifecycle Management > Update Status |
Allows users to view and click the Status button in the Lifecycle tracker, to advance an asset to its next lifecycle stage. Without this permission, the button is not shown. |
Standard | Contributor |
- The Assessments > Conduct Assessments global permission.
- The Asset > Lifecycle Management > Assessment resource permission on the relevant community or domain.
Recommended licensing approach
For organizations with a broad user base, a two-tier approach works well for Lifecycle management:
- Contributor: Assign to users who need to conduct assessments or participate in lifecycle workflows. This typically covers the majority of users in a deployment.
- Creator: Reserve for users who manage the asset lifecycle, such as those who advance lifecycle statuses, add sign-off activities, or act as approvers. This is typically a smaller core team.
This helps avoid over-provisioning Creator licenses across the organization.