orchestrator
2022.10
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Allocating Host Licenses to Tenants
Orchestrator User Guide
Last updated Dec 9, 2024
Allocating Host Licenses to Tenants
If you have a pool of user, robot, and service licenses at the host level, you can allocate a custom number of those licenses to your organizations, thus licensing those organizations.
For more information about the types of licenses, see About licensing.
After you allocate licenses to organizations, organization administrators can further allocate those licenses to the accounts and tenants in their organization, as needed.
Note:
- The instructions on this page are for system administrators and refer to license allocation at the host level.
If you are an Orchestrator administrator, see Licensing instead.
- The amount of time it takes for changes to license allocation for an organization to be propagated to the Orchestrator tenant
and to AI Center is set by the
License.Cache.Expiration.Minutes
parameter and it is set to 5 minutes by default. Do not change this setting to avoid causing configuration errors.