Note The content in this topic is nearly identical to the AI Governance roles and permissions content. The only difference is the product name; this topic refers to AI Command Center.
Global permissions
| Global permission | Description | Required license | New license |
|---|---|---|---|
|
Product Rights > AI Governance |
Allows users full access to the AI Command Center. Certain tasks, however, require specific permissions. |
Read-only | Viewer |
|
AI Governance > Register Agent Contract |
Allows users to create Agent Contracts. The AI Business User global role has this permission by default. The creator is automatically assigned the Owner resource role on the new Agent Contract asset. This permission only applies if the AI Agent contracts setting is switched on; for complete information, go to About Agent Contracts. |
Read-only TBC | Viewer TBC |
| AI Governance > Manage dashboard layout |
Allows users to hide, show, and reorder widgets within the AI Command Center dashboards. |
Standard | Creator |
|
AI Governance > Register AI Agent |
Allows users to register AI agents. | Read-only | Viewer |
|
AI Governance > Register AI Model |
Allows users to register AI models. For users without this permission, the Register AI Model button is not shown on product pages. | Read-only | Viewer |
| AI Governance > Register AI use case |
Allows users to register AI use cases. For users without this permission, the Register AI use case button is not shown on product pages. |
Read-only | Viewer |
| AI Governance > View summary dashboard |
Allows the user to access and view the AI Command Center dashboards. |
Read-only | Viewer |
| Workflow > Participate in workflow |
Allows users that meet workflow task configuration requirements to be assigned and complete workflow tasks. |
Read-only | Contributor |
| Workflow > Start workflow |
Allows users that meet workflow configuration requirements to start workflows. |
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 | Viewer |
| Assessments > Conduct Assessments |
Allows users to conduct, edit, copy, delete, and make assessments obsolete, including public assessments and those that they own or are assigned. Note An administrator can optionally restrict who can start a specific assessment to users with certain resource roles on the linked asset. When a Who can start this setting is configured on the assessment template, it applies in addition to the Conduct Assessments global permission described above. This is an opt-in template setting; if it isn't configured, any user with the global permission can start the assessment. For more information, go to Collibra Assessments.
|
Standard | Contributor |
| Product Rights > System Administration |
Allows users to manage all sections of the Collibra Settings, including the general settings, operating model, roles, permissions, users, groups, and workflows. You need this permission to work with the AI Command Center Customization settings. |
Standard | Creator |
Tip If you want to grant a user the ability to access AI Command Center in a read-only way, meaning without the ability to register AI use cases, AI models, or AI agents, and without the ability to participate in assessments, you can assign the user a custom global role that has only the Product Rights > AI Governance global permission.
Global roles
The following table describes the out-of-the-box AI Command Center-related global roles.
For an overview of the global permissions configured for each of these global roles, go to Global permissions.
| Global role | Description | Resource ID |
|---|---|---|
| AI Business User | A user who creates, updates, and views AI use cases. | 00000000-0000-0000-0000-000000005096 |
| AI Governance Admin |
A user who configures AI Governance settings. |
00000000-0000-0000-0000-000000005107 |
| AI Governance Viewer |
A user who can view necessary AI Governance-related information without needing a Contributor or Creator license. |
00000000-0000-0000-0000-000000005106 |
| AI Producer | A user who contributes to building AI solutions and who creates, updates, and views AI agents and AI models. | 00000000-0000-0000-0000-000000005102 |
Resource permissions
The following table shows resource permissions that are necessary for carrying out specific tasks in AI Command Center.
| Resource permission | Description | Required license | New license |
|---|---|---|---|
|
Register AI models and AI agents via the product UI or the CLI. |
Standard | Creator |
|
Asset > Lifecycle Management > Sign-Off |
Allows users to add sign-off activities to AI Model Version and AI Use Case assets. |
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 | Creator |
| Asset > Update |
Allows users to update the rules of an Agent Contract, by pushing a new version through their AI assistant, as described in Create or update an Agent Contract. The Owner resource role has this permission, and the creator of an Agent Contract is automatically assigned it. |
Standard TBC | Creator TBC |
|
Add, edit, or delete attributes and relations via the asset page or an asset view. |
Standard | Creator |
When submitting an assessment, you have to specify a domain in which you want the Assessment Review asset to be created. Whichever domain you specify, at least one user must be assigned the Business Steward resource role on that domain (or its community). The user submitting the assessment does not have to be the Business Steward.
Recommended licensing approach
For organizations with a broad user base, a two-tier licensing model works well for AI Command Center:
- 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.