Roles and permissions for AI Tools

Set up roles and permissions for the Automation Admin, Pro Developer, and Citizen Developer to ensure they can access features based on their roles and tasks.

These are personae for AI Tools and a high-level overview of their tasks.

Personae for AI Tools

The following sections describe the roles and permissions for each persona in details.

An Enterprise Platform license is required to enable AI Tools capability for AI Agent Studio.

Note: After procuring the Enterprise Platform license, the IT Admin, with the AAE_Admin role, would create a role for the Automation Admin. After which, the Automation Admin would create roles and assign permissions to other users based on their tasks.

Automation Admin

Role: AAE_Basic, Automation Admin Custom role

License: Attended Bot Runner

The Automation Admin Custom role requires following permissions:
Automation Admin Custom role Permissions
Automation Admin Custom role
  • Model connections > View Model connections
  • Model connections > Manage Model connections
  • View Settings > Manage Settings.
  • Credentials > Manage my credentials and lockers (select all check boxes)
  • Administration > Settings > AI Data Management > Data logging settings > Enable > Allow users to disable logs on AI Skills.
A few points to keep in mind:
  • The Automation Admin enables the AI Data Management > Data logging settings setting for other users. Once this is enabled for the users, the Automation Admin can also enable the AI governance settings for them.
  • The Automation Admin creates and assigns the Pro Developer and Citizen Developer Custom roles to the users as per their tasks.
  • As per requirement, the Automation Admin can enable these AI governance permissions for any persona: AI governance > View AI prompt logs and AI governance > View AI event logs.

Pro Developer

Role: AAE_Basic, Pro Developer Custom role

License: Bot Creator

The Pro Developer Custom role requires following permissions. The Automation Admin creates and assigns this role:
Pro Developer Custom role Permissions
Pro Developer Custom role
  • Model Connections > View Model Connections
  • View Settings
  • Credentials > Manage my credentials and lockers > View and edit ALL credentials attributes value
  • Bots > View my bots.
    Note: Check all the check boxes for the View my bots setting after which, the Bots tab gets enabled. Select all check boxes for the Bots tab as well. This will ensure folder-level permissions for the Pro developer.
  • AI Data Management > Data logging settings > Enable > Allow users to disable logs on AI Skills.
    Note: Once the Automation Admin enables this setting for the Pro Developer, they would see the Data logging enabled switch in the AI Skills screen. This gives them the ability to enable or disable data logging for that specific AI Skill which would result in displaying or masking all prompt data such as the prompt-text, response, and parameter settings in the AI governance > AI prompt log list.

Citizen Developer

Role: AAE_Basic, Citizen Developer Custom role

License: Bot Creator

The Citizen Developer Custom role requires following permissions. The Automation Admin creates and assigns this role:
Citizen Developer Custom role Permissions
Citizen Developer Custom role
  • Model Connections > View Model Connections
  • Credentials > Manage my credentials and lockers > View and edit ALL credentials attributes value
  • Bots > View my bots
    Note: Check all the check boxes for the View my bots setting after which, the Botstab gets enabled. Select all check boxes for the Bots tab as well. This will ensure folder-level permissions for the Pro developer.

A Pro Developer can also perform similar tasks as the Citizen Developer. In this case, the Automation Admin would have to assign the Citizen Developer Custom role to the Pro Developer.