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 may continue to reference Automation Anywhere Robotic Interface (AARI)] within the product.

There are two main types of users that run Automation Co-Pilot. They can be broadly categorized into users who access the Control Room to build processes in the Process Composer, and end users that run automations using Automation Co-Pilot from the cloud or desktop.

Users and their roles

Configure users with the proper roles and permissions and assign them the AARI license to start using Automation Co-Pilot. The primary users involved in the configuration stage are as follows:

Control Room Admin: They can create users and assigns Automation Co-Pilot roles (AARI Admin, AARI Manager, and AARI User) with the AARI licenses.
Create users for Automation Co-Pilot
AARI Admin: They can create scheduler users and allocates Control Room resources required to run a process.
Configure scheduler user for Automation Co-Pilot

The following table illustrates the relationship between users, roles, and the permissions they have while using Automation Co-Pilot.


User	Role	Permissions
Control Room Admin	AAE_Admin	Create users with AARI license and assign roles.
Bot Creator	AAE_Basic	Create a process. Check in a process. Check out a process. Run a private process. Delete a process. Import a process. Export a process.
AARI Admin	AAE_Robotic Interface Admin	Configure scheduler user and allocate Control Room resources (device pool and unattended Bot Runners) to a process in the configuration setup stage. Perform the following global team and process management tasks in the process deployment stage: Create, view, and modify all teams. Assign teams to processes.
AARI Manager	AAE_Robotic Interface Manager	Create and view teams. Note: Requires the AARI license. Add members to or remove members from the teams. Assign owners to the teams. Function as default admin for the teams they create. Request AARI admin to assign their team to processes.
AARI User	AAE_Robotic Interface User	Create and access requests. Submit and access tasks.

Team roles and permissions

The following table lists the users, and their roles and permissions in a team.

Note: These roles require the AARI license.


Team role	Control Room role	Team type	Permissions
Note: The AAE_Robotic Interface Manager role sets the AARI Manager to automatically have an Admin team role. A license is required.	AAE_Robotic Interface Manager	Shared	Create View all Delete all Assign all Modify team
	AAE_Robotic Interface Manager	Private	Create View all Delete all Assign all Modify team
Owner	AAE_Robotic Interface User	Shared	Create View all Delete all Assign all
Owner	AAE_Robotic Interface User	Private	Create View all Delete all Assign all
Member	AAE_Robotic Interface User	Shared	Create View all Delete Assign all
Member	AAE_Robotic Interface User	Private	Create View Delete Auto-assign

Example

Consider two teams, Finance and HR, and their team roles as listed in the following table:


Finance (private)		HR (shared)
User	Role	User	Role
User A	Owner	User X	Member
User B	Member	User Y	Member
User C	Member	User Z	Owner

For any process, keep in mind the following:

User A can view and delete all the requests created inside the team Finance.
Users B and C can view and delete only their requests inside the team Finance.
Users X, Y, and Z can view all the requests but can delete only their request inside the team HR.
User Z can view and delete all the requests created inside the team HR.

Automation Co-Pilot workflow

Workflow map: Click the following schematic image to view the Automation Co-Pilot workflow in an interactive visual format:

See also, Create a team and assign roles to team members

Automation 360

Users and team roles for Automation Co-Pilot