---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Robot license distribution

# Robot license distribution in RPA Hub {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
As a user who has the sn_rpa_fdn.rpa_admin role, you can create, write or delete robot license distribution record to define the consumption and distribution of licenses in your
organization. You can create only one robot license distribution record per domain in a domain separated instance. Once you create this record, you can edit it, but you can't delete it.

If the instance you are using is not domain separated, then you can create only one robot license distribution record in global domain.

For more information about creating a robot license distribution record, see [Create a robot license distribution record in RPA Hub](https://www.servicenow.com/docs/P30r7eNlC1VHsK7C~oq_CQ "Define the consumption and distribution of licenses by creating a robot license distribution record in RPA Hub.").

For more information about executing RPA scripts, see [Re-evaluate license distribution by executing RPA scripts](https://www.servicenow.com/docs/VHoFSYx47s6vmgcQddqmXg "Run the Robotic Process Automation (RPA) script on demand to validate and unlock the robots in a domain and its child domains.").

For unattended robots, licenses are available for the robot that is created in the current domain only. Release managers or administrators create unattended robots and associate them with Windows or virtual machines. An unattended robot is mapped to only one Windows or virtual machine.

For attended robots, licenses are available for the domain that is associated to the robot.
Release managers or administrators create attended robots and associate them with users. If the
auto assignment of Attended Robot property
(sn_rpa_fdn.allow_rda_robot_auto_assignment) is enabled, the robot records are automatically
created on a first-come, first-served basis. An attended robot is mapped to only one user.

To unassign a user, you must retire the associated attended robot. For more information, see
[Unassign an attended user or group from an attended bot process in RPA Hub](https://www.servicenow.com/docs/kxptGRmX4Rvmyt0P8JLAFg "Unassign an attended user or a group from an attended bot process if the user is moving out of the business process."). To remove a user from a group, contact your
organization.

To retire a robot if the robot machine is not working appropriately, retire the associated
unattended robot. For more information, see [Retire a robot in RPA Hub](https://www.servicenow.com/docs/2EvvFQRxI8Ze0UbvPGn_Lw "Retire a robot to turn it off. It is one of the life-cycle stages of a robot. After you retire a robot, it cannot be used further.").

You can update a robot license distribution record. For more information, see [Update a robot license distribution record in RPA Hub](https://www.servicenow.com/docs/rDYxlme_0LNb3mzO7oVzHA "Update a robot license distribution record in RPA Hub to evaluate the consumption and distribution of licenses in your organization.").