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.
    Note: Automation 360 supports custom role creation by allowing all permissions to be non-default and editable. However, for releases before version v30, system-created roles such as, AAE_Admin are mandatory. For more information, see System-created roles.

    Create users for Automation Co-Pilot

  • The AAE_Robotic Interface Admin creates teams and scheduler users to allocate Control Room resources, and assigns processes to users and teams.

    Configure scheduler user for Automation Co-Pilot

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
Admin persona AAE_Admin Operates in the Control Room to:
  • Create and manage users.
  • Assign Automation Co-Pilot license to users.
  • Create and assign roles to users.
AAE_Robotic Interface Admin Operates in Automation Co-Pilot to:
  • 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.
Marcus persona AAE_Basic Operates in the Process Composer and Automation Co-Pilot to:
  • Create a process.
  • Check in a process.
  • Check out a process.
  • Run a private process.
  • Delete a process.
  • Import a process.
  • Export a process.
Tomas persona AAE_Robotic Interface Manager Operates in Automation Co-Pilot to:
  • Create and view teams.
    Note: Requires the Automation Co-Pilot 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 Automation Co-Pilot admin to assign their team to processes.
Bria persona AAE_Robotic Interface User Operates in Automation Co-Pilot to:
  • Create and access requests.
  • Submit and access tasks.