- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- Tenants and services
- Accounts and roles
- External applications
- Notifications
- Logging
- Troubleshooting
Assigning licenses to tenants
This article walks you through the steps for allocating robot and service licenses from your organization's license pool to tenant license pools.
You can assign licenses to tenants:
- when you create a tenant
-
for an existing tenant, by going to the tenant's Licenses page, as described on this page.
Note:If user license management is disabled from organization settings, you must also assign user licenses to your tenants, in the same way as you assign robot and service licenses.
If this is the case for your organization, follow the instructions on this page to manage your user licenses as well.
You can view and manage the licenses that are assigned to each tenant separately.
For each tenant:
- In the top right, click Edit allocation.
The Edit license allocation panel opens at the right of the page:
Breakdown of the license allocation windowRobot licenses (in the Orchestrator section) and service licenses for the services in this tenant are displayed, grouped by the service.
If user license management is disabled, user licenses are also available in this panel.
The panel closes and the Licenses page shortly refreshes to display the updated license quantities.
Although license management is typically performed from the administration interfaces, in Orchestrator you do work with a particular type of license: the runtime, which is a service license for robot use.
Runtimes are the licenses you need to run unattended automations. You allocate runtimes when you create a machine object in Orchestrator. There are two aspects to know when allocating runtimes:
-
Number of runtimes: You can assign a custom number of runtimes to a machine template, which determine the number of processes that can run at the same time on a machine.
The number required runtimes is given by the number of jobs you want to allow to be executed at the same time on this machine; it is not impacted by the number of robots on the machine.
Let's say you have a machine template with 10 Production (Unattended) runtimes allocated to it. For each workstation that is connected using the machine key of that template, 10 Production (Unattended) runtimes are reserved from the available licenses at the tenant level, allowing for executing 10 jobs at the same time. From these reserved runtimes, a runtime is only in use during job execution. So if you connect 4 machines to Orchestrator using that template, you need and reserve 40 runtimes at the tenant level. With, for example, 25 jobs running, 25 out of the 40 reserved runtimes are in use, leaving 15 runtimes that are reserved, but unused.
- Types of runtimes: The types of runtimes that are assigned to a machine object determine the types of processes that can run on that machine.
