Monitoring license allocation

From the Home page

The homepage displays license allocation at the organization level.

Check the License Allocation section to see the number of allocated licenses out of the total number of purchased licenses in your organization. Switch between the available tabs to change the displayed license information per license type.

From the Licenses page

You can see license allocation details from the platform-level Licenses page, for either the entire organization, or just one tenant:

• For the entire organization, access Admin > organization > Licenses.
• For a particular tenant, access Admin > tenant > Licenses.

The Licenses page displays the number of all purchased licenses in your organization. Switch between these tabs to view license information per license type:

• Users - displays user licenses.
• Robots & services - displays service capacity items, such as runtimes, Data Service units, and Computer Vision licenses.
• Consumables - displays licensed consumption units, such as AI Units, Robot Units, and Integration Service API calls.

If a license type is not displayed, it means there are 0 licenses of that type purchased for your organization.

The Users and the Robots & services tabs

Hover over the progress bar on the Users and Robots & services tabs to see the number of allocated licenses out of the total number of purchased licenses in your organization.

The Consumables tab

Click the cards on the Consumables tab to see details about how your organization's or tenant's service consumption units are used per month or per year.

This is what you can expect to see depending on the level:

Level	Information	Further details
ORGANIZATION	The total number of units in the account	Their start date Their expiration date If the units reset monthly, their reset date
	The total number of consumed units vs. the total number of available units	N/A
	Usage details for AI units1	The total number of consumed units, counted from the start date, and split per service which registers the consumption of such units. The number of units consumed each month, counted over the past 12 months, and split per service which registers the consumption of such units.
	Usage details for robot units	The number of units consumed each month, counted over the past 12 months, and split between Serverless and VM robots. The number of units consumed during the current month by Serverless robots.
	Usage details for Integration Service API calls	The number of calls consumed each month, counted over the past 12 months, and split based on their type: API calls bundled with license or API calls purchased as a dedicated bundle.
TENANT	The total number of units allocated to the selected tenant	Their start date Their expiration date If the units reset monthly, their reset date
	The total number of consumed units vs. the total number of available units	N/A
	Usage details for AI units1	The total number of consumed units, counted from the start date, and split per service which registers the consumption of such units. The number of units consumed each month, counted over the past 12 months, and split per service which registers the consumption of such units.
	Usage details for robot units	The number of units consumed each month, counted over the past 12 months, and split between Serverless and VM robots. The number of units consumed during the current month by Serverless robots.

¹ You can see a detailed breakdown of AI units consumption across various products, projects, and hardware by checking out the AI units consumption overview Insights dashboard.

The Consumables tab

AI Units usage expanded

AI units consumption overview dashboard

Note:

• This feature is only available to Enterprise organizations.
• The dashboard is currently available as a preview.

Prerequisites

To access the AI units consumption overview dashboard, you must enable Insights for your tenant.

For more information, check the Getting started with Insights dashboards page.

Make sure you are using these minimum versions or higher:

• UiPath Studio and Robot: 2023.6
• UiPath.DocumentUnderstanding.Activities package: 2.9.1
• UiPath.DocumentUnderstanding.ML.Activities package: 1.28.2
• UiPath.IntelligentOCR.Activities package: 6.19.1
• UiPath.MLServices.Activities: 2.0.2

The AI units consumption overview dashboard, available under the Consumables tab at both the organization and the tenant level, dispays the number of consumed AI units. To display it, click View usage in the AI Units section.

The dashboard item corresponding to each tenant includes the following details:

• The tenant name and ID
• The number of consumed AI units from the tenant pool. This means that the consumption source, such as a Document Understanding project, belongs to a specific tenant.

  Data is only displayed if AI units have been allocated to tenants. Find out more about Allocating licenses to tenants.

• The number of consumed AI units from the organization pool. This happens either when there are no AI units allocated to a tenant and the consumption source belongs to a specific tenant, or when consumption happened by using the public endpoints, such as the Document Understanding public endpoints.
• A link to the corresponding Insights dashboard, which further breaks down AI units consumption per service, and provides details on the usage by project, folder, or operation. This covers consumption at the tenant level and only contains data from the respective region.

Permissions

• The organization-level dashboard is only visible for organization administrators.
• The tenant-level dashboard requires the Viewer permission in Insights.

For more information on how AI units consumption is reflected in Insights, check out the Insights documentation.

Note:

• Dashboard data is limited to information from the same region as that of the organization.
• Data is refreshed every 24 hours.
• The dashboard includes AI units consumption data for Document Understanding and AI Center.
• The default tenant's name may be displayed as Unknown in the following scenarios:
  • If the tenant was created while the organization was on the Community plan, but it was then moved to the Enterprise plan.
  • If data pertains to a different region than that of the organization.
  • If consumption data pertains to missing transactions, such as those with no job ID.
• Make sure you update your Robot and activity packages to the latest version, so that the dashboard can collect all required data points.
• In certain cases, the tenant name is displayed as Organization Level. This typically happens if Document Understanding consumption was done through API Key authentication, or if Document Understanding Cloud APIs were used.