Using a concept of a tenant to manage env lifecycle

Hello, I came across a configuration where a tenant is called “development” and “test”, and this appears as an attempt to separate the environments within a single Orchestrator installation. Can this possibly be right? Thx!

1 Like

Yah we can create a tenant for different instances like Dev, Test and prod
That’s how usually the enterprise orchestrator were bought in segregated way to handle the bots and respective machines of these three instances
While this applies the same for community edition as and we can create with such no of tenants to handle the different instances and their machines

Hope this would help you
Kindly correct me if I m wrong and let know for any queries or clarification
Cheers @Malgovita

Multitenancy is typically aligned with organizations or business units, and provides secure logical separation. Shouldn’t the “assets” construct be used to differentiate environments instead?