Manage roles and teams for Automation Co-Pilot

A variety of permissions are available to grant access to user-created roles and administer Automation Co-Pilot privileges to meet policies for security and organization.

Ensure that you have the View and manage MY teams and View and manage ALL teams permission (AAE_Admin) to create and edit respective teams. See, Create a role

Teams in Automation Co-Pilot

Automation Co-Pilot enforces role-based access control (RBAC). User-created roles can be customized for unique business needs and deliver specific privileges to focus product features on assigned roles.

Unlike system-created roles, administrators can create a role and customize permissions needed for a specific type of user. When creating a role, the following table offers details of the product behavior associated with permissions.

In addition to granting privileges, roles can be used as a group type in Automation Co-Pilot. Consider creating a role to be used as a valid input for a group (to include all users with the role) when assigning teams, tasks, or a process to users. All components of the product recognize the group and behave accordingly.

Team members and permissions

The following table lists the users, and their roles and permissions in a team.
Note: These roles require the Automation Co-Pilot Business User license.
Team role Control Room role Team type Permissions
Note: The AAE_Robotic Interface Manager role sets the Co-Pilot 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
Private
  • Create
  • View all
  • Delete all
  • Assign all
  • Modify team
Owner AAE_Robotic Interface User Shared
  • Create
  • View all
  • Delete all
  • Assign all
Private
  • Create
  • View all
  • Delete all
  • Assign all
Member AAE_Robotic Interface User Shared
  • Create
  • View all
  • Delete
  • Assign all
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.

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