Users and team roles for Automation Co-Pilot
- Updated: 2024/01/05
Users and team roles for Automation Co-Pilot
Users with specific roles and permissions can use different features in Automation Co-Pilot to automate business processes as per requirement.
Note: Roles, permissions, and licenses might continue to reference
Automation Anywhere Robotic Interface (AARI) within the product.
Users and their roles
The
admin should assign each user with respective roles, permissions and AARI license for
Automation Co-Pilot and the product features to run smoothly across
devices and business organization. Primary roles involved in this set up are as
follows:
- The Control Room Admin creates users and assigns Automation Co-Pilot roles (Co-Pilot Admin, Co-Pilot Manager, and Co-Pilot User) with the AARI licenses.
- The Co-Pilot Admin creates scheduler users and allocate any Control Room resources required to run processes.
There are two main types of users that run Automation Co-Pilot. They can be broadly categorized into developers that build bots and process automations using the Process Composer, and end users that run automations using Automation Co-Pilot.
The following table illustrates the relationship between users, system-created roles, and permissions for accessing Automation Co-Pilot.
Persona | Role | Permissions |
---|---|---|
AAE_Admin | Operates in the Control Room to:
|
|
AAE_Robotic Interface Admin | Operates in Automation Co-Pilot to:
|
|
AAE_Basic | Operates in the Process Composer and Automation Co-Pilot to:
|
|
AAE_Robotic Interface Manager | Operates in Automation Co-Pilot to:
|
|
AAE_Robotic Interface User | Operates in Automation Co-Pilot to:
|