New UiPath Automation Cloud Tenants are almost here!

Hello from the UiPath Automation Cloud team!

We wanted to follow up on our earlier summary “what’s next” post about the introduction of upcoming features with some more details on one that is going live shortly: Tenants. Today, this feature makes managing services across multiple tenants easier for our UiPath Cloud Automation for enterprise customers, but in the future, our community customers will also be able to add more services to their tenant.

As we presaged in the previous post, we will shortly be adding Tenants to the UiPath Automation Cloud, and a Tenant can contain multiple services. Previously, when you clicked the “add service” button in the portal, you actually created a new tenant with one service in it: Orchestrator – but you probably didn’t know it. Because Orchestrator was the only service (and you couldn’t add any others), we just showed them as a single entity, like here:

It started to get confusing, though, when we launched AI Fabric – a second service – recently, and it would certainly get more confusing as we add more services. So to simplify, we are evolving the UX to make it very clear which services are running in which tenants, and enable you to easily configure the individual services in a tenant.

In the example below, you see the new experience. It’s similar to the old experience, but see that now the HR tenant has Orchestrator and AI Fabric services , and the Marketing tenant has the same (but is shown collapsed – clicking the down arrow will expand the services out):

To access the service, simply click on the service name, either collapsed or expanded. So, to access Orchestrator in the HR tenant, just click on it. Tenants themselves are not clickable (they are not services) - so any configuration you need to do to them you can do from the icons on the right on the tenant name row.

The other change of note is that the “Add Service” button has subtly become the “Add Tenant” button, and it will come as no surprise that when you add a tenant, you can now choose the services that you add to it. Orchestrator is always selected, but you can also select other services (in this case, AI Fabric):

You are then able to assign the number of licenses you want for each of the services in the Tenant.

In the Tenants tab (under Admin), each service may offer administration option icons to the right when you expand the list, as you see below. For example, you can manage Orchestrator users and the API settings for the Orchestrator service within that tenant on the Orchestrator line. Incidentally, the addition of groups was another recent change we posted about that makes user management easier, so if you haven’t had a chance, read all about it here.

Overall, we hope this is an intuitive and relatively simple change that makes things cleaner and easier. When this change goes live we will update our detailed documentation on to reflect these changes and detail all the capabilities.

Thanks for being a UiPath customer!


Looks good!

One thing I miss (or haven’t been able to find) is the ability to prevent a user from seeing “licenses”, “users” and “API Keys”.
It isn’t very sensitive data but it would be great if we with a role have the opportunity to limit these things as well, business users don’t need access to that information, especially not API key.