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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Update a robot license distribution record

# Update a robot license distribution record in RPA Hub {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Update a robot license distribution record in RPA Hub to evaluate the
consumption and distribution of licenses in your organization.

## Before you begin

Familiarize yourself with license distribution in RPA Hub concepts. For more information, see [Robot license distribution in RPA Hub](https://www.servicenow.com/docs/8OXr0Cu7wff1rS5rcELEug "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.").

You must do this task in the classic environment.

Role required: sn_rpa_fdn.rpa_admin

## About this task

For example, a domain separated instance with top domain and two child domains has 20 unattended robot licences and 45 attended robot licences. In each domain, you could assign 5 unattended robot licences and 15 attended robot
licences. The Available from Parent field will show 10 unattended robot licences and 15 attended robot licences that are not yet assigned. When a robot is created in a child domain, a license is
automatically utilized in that domain. In a license distribution record of a child domain, the Utilized field will show the value as 1 and the Available to use or distribute field
will show the value as 4, which is remaining assigned licenses that are not yet utilized.

If you have more robots than the assigned licenses, then the instance or the specific domain (and its child domains) gets locked. Then, the robots do not execute automations in the current and child domains.

## Procedure

1. Navigate to AllRobotic Process AutomationAdministrationRobots License Distribution.
2. Open the license record that you want to update.
3. Update the following fields as appropriate.  
   {#update-license-record-rpa__table_pyx_mhd_4qb__entry__2}

   | Field | Description |
   |-|-|
   | Assigned (Unattended) | Total number of the assigned licenses for unattended robots in the current domain. This value must not exceed the value in the Available from Parent (Unattended) field. |
   | Assigned (Attended) | Total number of the assigned licenses for attended robots in the current domain. This value must not exceed the value in the Available from Parent (Attended) field. |
   [Table 1. Robot License Distribution form]

   {#update-license-record-rpa__table_pyx_mhd_4qb}
4. Select Update.
{#update-license-record-rpa__steps_arj_mgh_psb}
**Related tasks**   

* [Create a robot license distribution record in RPA Hub](https://www.servicenow.com/docs/OMU6McX8VTW4kRc~rYlrow "Define the consumption and distribution of licenses by creating a robot license distribution record in RPA Hub.")

*[\>]: and then