AI feature permissions
Assign the RBAC permissions that control access to AI features in Red Hat Developer Hub.
To control who can use each Developer Hub Intelligent Assistant AI feature, assign the feature-linked RBAC permissions that grant access to the chat, Notebooks, MCP tools, and skills.
Each feature uses a single permission that grants full access of that feature. Permissions do not separate create, read, update, and delete actions: a role either has full permission to use a feature or no access. All AI feature permissions use the use action.
| Permission | What it grants |
|---|---|
|
|
Use the Developer Hub Intelligent Assistant chat feature, including opening the chat window, sending messages, managing chat history, and saving and reusing chat prompts. |
|
|
Use the Developer Hub Intelligent Assistant Notebooks feature, including listing, reading, creating, uploading, querying, updating, and deleting Notebooks. |
|
|
Use the Model Context Protocol (MCP) tools, including listing MCP servers and managing their configuration. |
|
|
Use the Developer Hub Intelligent Assistant skills feature. |
Agent Skills permissions
| Permission | Action | What it grants |
|---|---|---|
|
|
|
View information about the Agent Skills that are available to the deployment. This permission controls visibility only. It does not control whether skills are loaded or whether configured skills influence answers. |
Example RBAC policy
The following example grants a team full access to all Developer Hub Intelligent Assistant AI features:
p, role:default/<team>, intelligent-assistant.chat, use, allow
p, role:default/<team>, intelligent-assistant.notebooks, use, allow
p, role:default/<team>, intelligent-assistant.mcp.tools, use, allow
p, role:default/<team>, intelligent-assistant.skills, use, allow
To grant access to a subset of features, include permissions for only those features.
Migration from previous permission names
If you are upgrading from Developer Hub 1.x, replace the previous lightspeed.* permission names with the feature-linked names. Developer Hub 2.1 grants each feature with a single permission and no longer uses individual action verbs such as create, read, update, or delete.
| Previous permissions (1.x) | New permission (2.1) |
|---|---|
|
|
|
|
|
|
|
|
|
This is a breaking change. Developer Hub 2.1 does not support the previous permission names. You must update all RBAC policies, conditional rules, and automation scripts that reference the previous lightspeed.* permission identifiers before you upgrade.