Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

The Settings page enables administrators to adjust tenant and global settings for Orchestrator. Make the changes on a per-tenant basis by using the tenant Settings page or for all your tenants by using the Settings page from the Orchestrator host portal.

Host settings apply to all tenants that did not update their settings with custom values.

General Tab


Field

Description

Application Settings

Time Zone - The time zone of the tenant. By default, this field is set to UTC.
The timezone list depends on the machine. To ensure that all the instances under a multi-node Orchestrator installation have the same timezone list, they must use the same operating system version.
🛈 It is recommended that the tenant and the Robots have the same time zone.

Language - The language of the Orchestrator user interface for the current tenant, including email notifications and alerts. This setting does not affect robot logs or event logs, which use your Windows language.

iconicon Custom header color - Select a color for the Orchestrator window header. This is useful for distinguishing between multiple Orchestrator tenants. The header color is selected by clicking the colored square to bring up your machine's color selector.

iconicon Custom logo - Enables you to upload your desired logo which appears in the Orchestrator window header. The accepted formats are .png and .svg, with a maximum file size of 1MB.
Note: A logo can be added at the host and/or tenant levels. The host setting will be overridden by any logo added at the tenant level.

In Automation Suite, changing the company logo is performed from the Organization Settings page. Learn more about managing organization settings in Automation Suite.

Client Binaries (Robot, Studio, Assistant) Auto-Update Settings

Auto-fill available product versions (host setting) - Configures the update policies to contain the latest versions of client binaries. If you need to manage update versions manually, disable this option and follow the steps described in this article.

Ignore auto-update status for robot machines that were offline for more than ___ days (tenant setting) - This excludes inactive machines from the update process and no longer takes them into account when the update status is reported.

Personal Workspaces (tenant setting)

Enable the Personal Workspaces feature.
Note: This action cannot be reversed, once the Personal Workspaces feature is enabled it cannot be disabled.

Enable Personal Workspace - Create personal workspaces for all users in a tenant that use a certain attended licensing profile, while also selecting the UI profile to be used for those users.

Standard Roles (tenant setting)

Create standard roles for modern folders. These roles empower you to leverage the benefits of user groups.

Click Create Role next to each of the roles you want to be automatically created.

Modern Folders

Enable the Account-Machine Mappings feature.

Classic Folders

Enable classic folders. Classic folders are deprecated. Enabling them is only recommended if you migrate from an on-premises Orchestrator deployment to Orchestrator services residing in Automation Cloud.

Email Setup

Enable alerts email.
For more information, see the Setting Up Email Alerts page.

Deployment Tab


Enables you to configure and secure a feed that can host automation packages.

Packages

Enables you to set an internal or an external feed in which automation packages can be maintained. By default, an internal feed is used. The feeds can be secured either by defining basic authentication credentials or by using an API key.

Field

Description

Internal

Must be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key.

External

Must be selected in order to use an external feed. The feed can be secured either by using an API key or basic authentication credentials.

Secure Deployment

Ensures that your automation packages are downloaded through a secure NuGet feed.

API Key

The key used to secure your feed against write operations such as delete or upload.

Deployment URL

The address where the NuGet feed is located.

Authentication

Enables you to specify the credentials for your basic authenticated feed.
Please keep in mind that both the username and the password used with the API Key option should be used in this case as well.

Libraries

Enables you to configure the feed to be used when working with library packages. Libraries can be published from Studio or manually uploaded by the user in Orchestrator and are stored within the chosen feed.

Field

Description

Only host feed (tenant setting)

Libraries are stored in the host feed and are available to all tenants which use it. The Libraries page is the same for one Orchestrator instance, meaning libraries are not isolated at the tenant level: each tenant has access to the other tenants' activity.
🛈 You cannot upload libraries from Orchestrator if this option is selected.
🛈 This option gives robot access to the host feed only.

Only tenant feed (tenant setting)

Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used.
🛈 This option gives robot access to the tenant feed only.

Both host and tenant feeds (tenant setting)

Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used.
🛈 This option gives robot access to both the host and tenant feeds.

Internal

Must be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key.

External

Must be selected in order to use an external feed. The feed can be secured using an API key.

Secure Deployment

Ensures that your automation packages are downloaded through a secure NuGet feed.

Deployment URL

The address where the NuGet feed is located.

API Key

The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages.
This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy.

Prerequisites for Using an External Feed Through a Proxy

If you want to use an external feed while you have a proxy server configured on Windows, the following are required beforehand:

  • Set the Load User Profile option for the Orchestrator application pool (Internet Information Services > Application Pools) to True.
  • Add the proxy settings you used to the NuGet.config file associated with the application pool identity account (C:\Users\[YourAppPoolIdentityAccountName]\AppData\Roaming\NuGet\NuGet.Config):
<config>
<add key="http_proxy" value="http://ipaddress:port" />
</config>

📘

Important

Note that the following settings are loaded only when the Robot Service connects to the server. Whenever they are modified you need to restart the UiRobotSvc service for the changes to take effect.

Security Tab


Robot

Field

Description

Run Disconnected Hours

Specify the number of hours a Robot can run offline, without checking for its Orchestrator license. By default, it is set to 0. The maximum accepted value is 168 hours.


Allow both user authentication and robot key authentication
(tenant settings)

When connecting the robot to Orchestrator allow both standard connections with tokens that don't expire and connections with tokens that expire.
The Sign in option is displayed in the Assistant allowing users to connect Studio and the Assistant to Orchestrator using their credentials.

Enforce user authentication, disable robot key authentication (tenant setting)

When connecting the robot to Orchestrator allow only connections with tokens that expire. User login is required to make Orchestrator HTTP requests, run Attended Robots, or view processes in the Assistant.
Restrict attended robot authentication in the Assistant to interactive user sign-in.

Warning!: Secure authentication requires recompiling the workflows that use Orchestrator activities or make direct HTTP calls to the Orchestrator API utilizing v2020.10 activity packages or higher.

Scalability Tab


Specify if the Robot service should subscribe to Orchestrator's SignalR channels, and configure the transport protocols that work best for you. These settings are preserved upon upgrading.

SignalR (Robots)

Field

Description

Enabled

This toggle specifies if the Robot service subscribes to Orchestrator's SignalR channels or not. By default, this setting is enabled, and all available channels are selected:
WebSocket
Server-Sent Events (SSE)
Long Polling

When all transport channels are enabled, the best available transport is automatically selected, in the following priority order: WebSocket > Server-Sent Events > Long Polling. If the first protocol is not available for any reason, the next in line (if enabled) is used to facilitate the communication between Orchestrator and Robot.

WebSocket

When selected, enables the WebSocket transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This is the highest protocol used in the order of priority due to its performance and support for simultaneous communication in both directions - from the Robot service to Orchestrator and vice versa.

This option cannot be used if the SignalR (Robots) feature is not enabled.

Server-Sent Events (SSE)

When selected, enables the Server-Sent Events (SSE) push technology to be used to connect the Robot to Orchestrator's SignalR channels. This is the first backup in case WebSockets is not available for any reason.

This option cannot be used if the SignalR (Robots) feature is not enabled.

Long Polling

When selected, enables the long polling transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This protocol is used in case the WebSockets and SSE ones are not available.

This option cannot be used if the SignalR (Robots) feature is not enabled.

Non-Working Days Tab


Tenant-level functionality.

Define a list of non-business days, per tenant, on which you can restrict triggers from running. This means that, during public holidays, weekends, or any other day on which normal business activities are not being carried out, your long-run schedules can be configured such that they don't trigger. Once the defined non-business days are over, the triggers launch as usual.

In order to apply these restrictions to your triggers, you need to select the non-working day calendar when configuring triggers. All changes you make on the Non-Working Days tab affect all triggers that use that calendar.

📘

Note:

Non-working day restrictions are disabled for triggers on a timezone different than the timezone set at tenant level (Settings > General). A tenant without an explicitly defined timezone inherits it from the host.

For more details on how to manage non-working days, click here.

Updated about a month ago


Settings


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.