How to create tenant in orchestrator?
May I ask the tenant use case? like what scenario we should consider to enable tenant.
Multi-tenancy enables you to create a custom number of tenants and isolate all their data (logs, reports etc.),
with only one instance of Orchestrator. This feature facilitates automating different departments from your
company and ensures the desired authorization of Orchestrator data per department.
To enable multi-tenancy you have to set the Tenant.Registration.Enabled parameter to true. If this is
set to true, a new field is displayed on the Orchestrator Log In page.
Thanks! for the reference.
- quick question about Tenants. Has the Tenant impact the Orchestrator’s bot handling capacity?
Let say from the Architecture perspective (from the guideline), 1 Uipath Orchestrator would able to handle 100-200 bots. If we split into muti tenants from the single platform, does it mean muti tenant can only manage bot <= 200 bots in total? (Despite of HW capacity).
Yes, it does… the db is a bottleneck…though there will be an option in the future to use different databases per tenant.
I will need to think about balancing tenants per Orchestrator.
Thank you very much to ddpadil too.
Can you please elaborate on how the DB is the bottleneck and also does multi tenancy help to run more bots simultaneously on VM. Would appreciate if you have any thoughts on when it should be used?
How many tenants could we create in one orchestrator? Is their any limit?