orchestrator
2022.4
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- 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
- About the host level
- Managing system administrators
- Managing tenants
- Allocating Licenses to Tenants
- Allocating host licenses to organizations
- Configuring system email notifications
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- Troubleshooting
Allocating host licenses to organizations
Orchestrator User Guide
Last updated Oct 9, 2024
Allocating host licenses to organizations
This page describes how to license organizations from the host-level pool of licenses.
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.
After you allocate licenses to organizations, organization administrators can further allocate those licenses to the accounts and tenants in their organization, as needed.