Welcome
Administering multitenancy for service providers
Configure and administer a HCL Universal Orchestrator multitenant environment.
Tenant lifecycle
The tenant lifecycle defines the sequence of operational states a tenant moves through, from creation to permanent removal, and the events that trigger these transitions.

What's new
HCL Universal Orchestrator is constantly evolving to offer you the most comprehensive orchestration capabilities. For known limitations, workarounds, and contact information of HCL Customer Support, see Release notes.
What is HCL Universal Orchestrator
HCL Universal Orchestrator is a cloud-native workload orchestration and scheduling platform built on Kubernetes. Its microservices-based architecture enables the centralized orchestration of multi-cloud and hybrid environments from a single point of control.
Deploying and Administrating
All the information you need to deploy and administrate HCL Universal Orchestrator.
Using the UI
The UI is the HCL Universal Orchestrator interface, from which you can design your scheduling environment and monitor every process.
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Orchestrating from Mobile
You can use your mobile devices to manage quickly and easily your whole HCL Universal Orchestrator environment.
Monitoring
Take your environment under control.
Using REST API
Use REST APIs to easily integrate workload scheduling capabilities with external products and solutions.
Administering multitenancy for service providers
Configure and administer a HCL Universal Orchestrator multitenant environment.
- Multitenancy architecture
  The multitenancy architecture uses a database-per-tenant model, a robust tenant identification mechanism, and secure sharing of backend services to achieve strict data isolation and operational efficiency.
- Enable and configure multitenancy
  Enable the multitenancy architecture and set its core parameters through the Helm deployment configuration.
- Create a new tenant
  Create a new tenant instance using the Tenant Manager console. You set the core tenant identifier, resources, and administrative user access during this process.
- Tenant lifecycle
  The tenant lifecycle defines the sequence of operational states a tenant moves through, from creation to permanent removal, and the events that trigger these transitions.
- Tenant Manager UI reference
  A guide to the Tenant Manager interface elements, including the tenant list columns, creation form fields, and their technical constraints.
- Multitenancy configuration parameters
  A reference list of the parameters used to configure multitenancy in the values.yaml file. Use tenants to represent customer instances in the system.
- Tenant manager RESTful APIs: Authentication using OAuth 2.0 tokens
Uno AI Pilot
Welcome to the HCL Universal Orchestrator AI Pilot documentation. This resource is designed to guide you through everything you need to know about using UnO AI Pilot effectively. You will find detailed instructions, feature overviews, and helpful tips to ensure you get the best experience with UnO AI Pilot.
UnO Agentic AI Builder
Troubleshooting
Recover your environment if any issue occurs.
Notices

Tenant lifecycle

The tenant lifecycle defines the sequence of operational states a tenant moves through, from creation to permanent removal, and the events that trigger these transitions.

Each state determines a tenant operational status and permitted actions. A state machine governs the lifecycle, with administrative actions or automated system processes triggering transitions.

Tenant types

Tenants are categorized by type. The type influences the lifecycle, particularly regarding expiration. Available types include TRIAL, QA, DEV, PROD, and INTERNAL.

The primary functional distinction is between TRIAL tenants and all other types. A TRIAL tenant has a default expiration period, after which it automatically moves to an inactive state. Other tenant types do not expire automatically unless explicitly configured.

Tenant states

A tenant exists in one of three states. A service provider administrator manages these states using the Tenant Manager.

ACTIVE: The standard operational state. The tenant is fully functional, and users can perform operations.
INACTIVE: A suspended state where tenant operations are paused. A tenant becomes inactive if an administrator manually deactivates it or if it reaches its expiration date. In this state, users can access the UI but cannot perform operations. A tenant returns to the ACTIVE state automatically upon license renewal or manually by a service administrator.
REMOVED: In this state, the system permanently purges tenant data. A tenant moves to the REMOVED state automatically after it remains inactive for a specific configured period. Alternatively, a tenant owner can request immediate service termination by providing a unique removal key. The owner must obtain this key from the Tenant section of the system settings page in the tenant UI. Once removed, no further administrative actions are possible.

State transitions

Specific events trigger moves between states. A new tenant starts in the ACTIVE state. An administrator can manually transition a tenant between ACTIVE and INACTIVE.

Expiration automatically transitions an ACTIVE tenant to INACTIVE. An administrator can manually reactivate or delete an inactive tenant. The system can also automatically transition an inactive tenant to REMOVED after a pre-defined cleanup delay.