Introduction

This functionality allows you to have multiple Orchestrators within one organization, choose which one to publish bots to, and manage those bots independently of each other. The ability to have multiple Orchestrators is useful, for example, for MSPs for which the separation of work environments of different clients is an important aspect. Also, multiple Orchestrators allow you to have a production and test environment in the same organization, which in turn simplifies the process of developing and maintaining RPA technology in a company.

Setting up multiple Orchestrators

Adding multiple Orchestrators to one Team

There are two ways you can have multiple Orchestrators in the same team:

• Multiple Orchestrators can be part of your plan.
• Additional licenses can be requested as an Add-on.

To add multiple Orchestrators, you must have the "Administrator" role and order an extra Orchestrator Add-on. Follow these steps:

1. On the User Portal, go to the "Billing" page → "Teams"

2. Scroll down to the "Add-ons" tab

3. Click on "Manage Add-ons"
   
4. On the right side, click on the "Order now" button to request an extra "Add-on Orchestrator SaaS".
   

Managing multiple Orchestrators

How to use another Orchestrator:

1. On the User Portal, navigate to "Orchestrator Saas" → "Dashboard"
2. On the upper right side of the screen, you can see the drop-down list where you can change the Orchestrator you are using.
   
3. To rename an Orchestrator, go to "Settings". Click the pencil icon to edit directly in the field.
   

Operating multiple Orchestrators

Publishing bots

After creating a bot or opening an already existing one, you can select the desired Orchestrator when publishing the bot via Studio Pro.

Connecting a Bot Runner

Suppose your organization has three Orchestrators. Thus, to connect Bot Runner, a user with access to Orchestrator must:

1. Generate a token in Orchestrator 1.
2. Insert the token into Bot Runner.

The result is as follows:

1. The user sees the Bot Runner in Orchestrator 1.
2. The Bot Runner does not appear in Orchestrator 2 or Orchestrator 3.
3. A Bot Runner connected to Orchestrator 1 can be assigned to bots published to Orchestrator 1.
4. A Bot Runner connected to Orchestrator 1 cannot be assigned to bots published to Orchestrator 2 and Orchestrator 3.

You can also publish the bot to all purchased Orchestrators at once. Learn more about publishing bots in this article.