- First Time Configuration
- Host Administration
- Organization Administration
- Accounts and Roles
- Licensing
- Notifications
About licenses
Learn about UiPath's licensing model, the types of licenses, and common licensing terminology to help you understand how to allocate your available licenses.
Commercial Model
UiPath's commercial offering provides multiple SKUs that allow for flexibility when choosing how to deploy and use UiPath software. See the UiPath Licensing Portal for more information about our available SKUs.
To learn more about user licenses, see:
- User licensing for general information
- The documentation of each product for details about a user license that is specific to that particular product
To learn more about these types of licenses, see Service licensing.
Licenses are cascaded down as follows:
-
Acquire one license to distribute centrally from the host level.
-
License each organization separately.
-
(Optional) For certain products, acquire standalone licenses.
License management is performed in either the Licenses page of the host portal (by a system administrator) or in the Admin > Licenses page of Automation Suite (by an organization administrator).
This enables you to license multiple organizations using a single license. It aggregates multiple licenses, making it ideal for being distributed across your organizations.
Only a system administrator can manage this type of license. System administrators can activate the license from the Licenses page while license allocation is done from the Organizations page of the host portal.
In this scenario, you have a license file for one organization.
This type of license is activated at organization level, by an organization administrator, from the Admin > Licenses page in Automation Suite. The organization administrator can then distribute licenses to each tenant within their organization.
You can choose to license only some of your organizations from the host-level and have other organizations license themselves at the organization level.
For products that are not included in Automation Suite, such as UiPath Robot and UiPath Studio (and its variants), this type of licensing allows you to license users with a license key.
You cannot track this type of licensing centrally from Automation Suite.
Why use standalone licensing
- You did not have Automation Suite to allow centralized license management when you acquired the products that you licensed separately and want to continue to use standalone licensing.
- You have RPA developers who work with multiple Orchestrator instances that are licensed by different entities. Standalone licensing allows them to license the product locally and then use the Stand-alone license option in the product to prevent them from consuming licenses from your license pool.
By default, you are notified by email at 180, 90, 30, 14, 7, and 1 day before the license expires. You can configure these values using the app setting.
At host level, for single licenses distributed across multiple organizations, only the system administrator receives these email alerts. At organization level, all the active users with the License - View permissions receive them. The emails are localized per user.
Grace period
Your license might include a grace period. If it does, you are notified about it at logon, and can renew the license without experiencing any service disruptions. If it does not, your robots stop working upon expiry.
