Automation 360 licenses
- Updated: 2024/07/18
Automation 360 licenses
The All Licenses page displays detailed information about current product and device licenses.
Product licenses
The Automation Anywhere Control Room is the web-based application at the center of the Digital Workforce Automation providing enterprise-wide management and control. The Control Room ensures reliable, scalable, and secure bot development and execution. From this central vantage point, operators can receive tasks from the Bot Creator and push to the Bot Runners for execution with simple mouse clicks. The Control Room monitors and audits all scheduled and running bots, in real time.
The Control Room provides an automated mechanism for tracking and controlling the use of licensed software across Bot Creators and Bot Runners, addressing NIST Change Management CM-10.
Device licenses
The device licenses section shows the number of licenses purchased, used, and available across all automation Control Room instances. In case of Cloud licensing, the Control Room licenses page also shows the number of licenses consumed from Control Room instances belonging to the customer.
The table below shows the different types of licenses supported by Automation 360 Control Room.
| License | Permission |
|---|---|
| Bot Creator | Users with this license can develop, edit, schedule, and
trigger automation for testing. Additionally, these users can run bots in the following ways:
|
| Unattended Bot Runner Run-time license | Users with this license can perform all automation tasks
that attended users can perform. Additionally, this license can also be
used for Automation Anywhere Control Room deployment, centralized
scheduling, and API-based deployment. Note: Among
all the triggers, you can associate any trigger only with a user who
has a Bot Runner license. Also, for a user with
unattended Bot Runner license, if you associate
triggers such as Hot key, Interface, or Window, the following
conditions apply:
Note: Only users with Unattended Bot Runner Run-time license can run event triggers on a
device in a Disconnected state.
|
| Attended Bot Runner Run-time license | Users with this license can run automations on their devices. However, these users cannot run or schedule bots on another device. |
| Citizen Developer license | Users with this license can create and run automations (including automations with triggers) on their devices. |
| IQ Bot pages (Number of pages) | This license is required for uploading documents to Automation 360 IQ Bot. |
| Standard Forms pages (Number of pages) | This license is required for uploading documents for processing in Standard Forms. |
| Google Document AI for Document Automation (Number of pages) | Enables Document Automation users to process
documents in Google Document AI. Note: This metric is visible only to customers who purchased Google Document AI licenses through Automation Anywhere.
|
| Standard Forms for Document Automation (Number of pages) | This license is required for processing documents in standard forms in Document Automation. |
| Document Automation (Number of pages) | This license is to process documents in an Automation Anywhere (Pre-trained) model, including the User-defined document type. |
| Document Workspace (Number of pages) | This license tracks consumption for customers who brought their own license for Google Document AI or Standard Forms. |
| Classifier (Number of pages) | This license can be used to classify documents and pages leveraging the IQ Bot Classifier package. |
| Bot Insight | Bot Insight provides real-time, RPA
native analytics for both business insights and operational intelligence.
The Bot Insight license is purchased on a per-user basis. To access the Business dashboard, the user must be assigned this license. |
| Automation Co-Pilot for Business Users (Automation Co-Pilot) | Users with this license can be added to a Team for Process Composer consumption. This allows them to create requests and submit tasks within Automation Co-Pilot. |
| Discovery Bot | Process Discovery licenses must be purchased for use for business analysts and business users using Discovery Bot. Discovery Bot supports two licenses. The business analyst uses the process analyzer license to view and manage the metadata from all recordings within the process. The business user uses the process recorder license to view, record, and submit a process using the Discovery Bot recorder. |
| API Task | API Task license provides API Task executions and concurrency limits. They must be
purchased for use by business analysts and business who use API Tasks. The licenses can be updated to reflect changes
in entitlements, including adjustments to API Task
executions, concurrency limits, and display names for base and overage
packs. These changes impact both base entitlements and overage licenses.
Consumption counting and maximum concurrency entitlements will be
enforced when the over-consumption limit is reached. Every Cloud customer receives 100 API Task
executions per Control Room as their free base
entitlement. The base entitlement also includes two concurrent
executions, meaning you can run two API Tasks
simultaneously. For higher execution limits and additional concurrences,
you need to purchase the Enterprise Platform license. Note: Over-consumption is defined as the consumption
after the entitlement is consumed 100%. After the over-consumption
limit is reached, users will receive a notification and the exhausted
licenses will expire within 24 hours. |
| Intelligent Automation - Automator AI | This license provides entitlement for using generative AI features such as prompt to automate, suggest next action, and Generative Recorder. Purchase this license to continue to use such generative AI features. This section displays the number of recommendations purchased and consumed by the customer. |
| Enterprise Platform | This license provides enterprise-grade features to manage uber-scale automations, performance, and users for enterprise customers and automation partners. These enterprise-grade capabilities provide the scale and ease for driving automations across large organizations.Enterprise Platform license needs to be purchased separately by the customers. After you purchase this license, the Enterprise Platform product will be applied on all the Control Room instances available with the customers. Enterprise Platform |
For information about Document Automation licenses, see Understanding licenses in Document Automation.
License types
| License type | Description |
|---|---|
| User-based license | This license type is assigned to users to perform specific
tasks in the Control Room. The following types of user-based licenses are available:
You can also allocate the following licenses for the users:
Note: The number of licenses you will need
depends on the number of users who need to perform the above functions
for all the Control Room instances owned by the
customers. |
| Volume-based license | This license type is used to purchase licenses in bulk
depending on your organizational requirements. The following types of volume-based licenses are available:
|
| Feature-based license | This license type provides entitlements for different capabilities that are bundled together. For example, Enterprise Platform license or Automator AI license. |
RBAC on License Management
Access to License Management is deny-all and allow by exception based on roles and domains as defined in RBAC. Only those users who have access to License Management permission can view the entitlement details from the Automation Anywhere Control Room.
Baseline inventory controls: Bot Creators, Bot Runners, and Bots
The Automation Anywhere Control Room manages all automation operations. Inventory controls are maintained through the application of RBAC to establish a single point of control for Base Line Configurations (NIST CM-2), access restrictions for configuration management (NIST CM-5 and 6). Automated baseline reporting can be configured.
Licensing in high availability and disaster recovery
The license information that is centrally stored in the database or license cloud, is shared within High Availability clusters and across Disaster Recovery sites because synchronous data replication is configured between multiple Control Room servers.
HA and DR deployment models