Users and roles for Automation Co-Pilot
- Updated: 2024/08/08
Users and roles for Automation Co-Pilot
Users with specific roles and permissions can access different features in Automation Co-Pilot to automate business processes as per requirement.
Users and their roles
For product features to run smoothly across devices and the business organization, the
admin should assign each user with respective roles, permissions, and the Automation Co-Pilot licenses. These are the primary admin roles involved:
- The AAE_Admin creates users and assigns Automation Co-Pilot roles (for example, Interface Admin, Interface Manager, and Interface User) with the Automation Co-Pilot licenses.
- The AAE_Robotic Interface Admin creates teams and scheduler users to allocate Control Room resources, and assigns processes to users and teams.
There are two main user types in Automation Co-Pilot:
- Developers who build bots and process automations
- End users who run the developed automations
The following table describes the relationship between users, system-created roles, and permissions to access 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:
|