Workload Management (WLM) involves key components such as workload queues, device pools, and WLM bots, orchestrated by the Control Room to ensure efficient automation processes. Review user roles and permissions for WLM.

Components

WLM architecture consists of some essential components that work together to create a powerful, scalable automation environment.

WLM bots
Bots or automations deployed on attended or unattended devices that pull work items and run them.
Workload queue
Defined in the Control Room. Acts as a container for incoming work items (structured units of tasks). The output of each work item is saved as work item result in the queue.
Run-as users
In a WLM device pool or WLM queue configuration, you can assign a run-as user to specify which credentials the bot should use when logging into a machine to process work items.
Device pool
A device pools is a group of machines that executes your automated tasks.
Work item
Each work item is a record (for example, a row from a spreadsheet, an API payload) processed independently.
Control Room
Orchestrates queue management, task assignment, priority rules, and service-level agreement (SLA) adherence.

User roles and permissions

You can configure these roles and permissions to ensure that your WLM capabilities are securely and efficiently utilized across the automations.

User roles
  • AAE_Queue_Admin: To administer all queues
  • AAE_Pool_Admin: To administer the device pools
Note: Apart from these system roles, you can also create a custom role with the permissions you need to meet your WLM requirements.
Workload permissions
  • Create queues: Establishes a central repository for work items and defines the rules for their management and processing.
  • Manage ALL queues: The overarching administrative capability to oversee, monitor, and control all the workload queues configured within the automation environment.
  • Export queues: Enables you to extract the configuration details of one or more existing workload queues from the Control Room into a portable file format. For example, JSON, XML, or a proprietary Automation Anywhere format.
  • Import queues: Enables you to upload a previously exported queue configuration file into the Control Room.
Activity permissions
  • View My In Progress Activity: Enables you to monitor currently running processes in real-time.
  • View My Scheduled Bots: Provides visibility into upcoming automated tasks, enabling you to understand bot utilization patterns and plan accordingly.
  • Schedule My Bots to Run: Enables you to actively manage automation timelines by configuring when processes should be executed.
  • View and Manage All Scheduled Activity from My Folders: Provides oversight of all automation activities within your designated folders, enabling comprehensive Workload Management across multiple automation processes.
Bots permissions
  • View my bots: Grants you the ability to view and access information about your assigned or owned bots.
  • Run my bots: Enables you to actively execute assigned bots (tasks) on-demand or trigger them manually.
Device permissions
  • View and manage my Bot Creator, Bot Runner, and device pools: Provides oversight and control over your assigned devices.
  • Create device pools: Enables you to establish new groupings of devices for specific automation purposes.
  • Administer all device pools: Provides comprehensive control over the entire device pool infrastructure across the Control Room.
Considerations When using WLM user roles and permissions:
  • Least privilege principle: Always assign only the minimum necessary permissions to each user role. This enhances security and reduces the risk of accidental or malicious actions.
  • Folder-level permissions: Beyond global permissions, you can apply granular permissions to specific bot folders, queues, and device pools, allowing better resource utilization.
  • Licensing: You must have appropriate licenses (for example, Bot Creator, Unattended Bot Runner, Attended Bot Runner) in addition to role permissions to perform actions. For more details, see Automation 360 licenses.
  • Default roles: While the Control Room provides default roles (such as AAE_Admin, AAE_Basic, AAE_Pool Admin, and AAE_Queue Admin), you can create custom roles to align with your organization's specific operational model and security policies.