What an administrator turns on so that builders in a company account can build, test, and deploy Maestro Automate workflows.

This page is for administrators of a company's UiPath account. If you signed up yourself, your account is ready to use, and you can skip this page.

In a company account, builders can only work with Maestro Automate after an administrator turns on the services it uses. Automation Cloud, UiPath's cloud platform, groups a company's work into an organization, and each organization has one or more tenants, which are separate areas with their own services, users, and settings. The steps below apply to every tenant where people build workflows.

Turn on these services for the tenant. Managing services describes how.

Insights isn't required.

Builders create, test, and deploy their first workflows in a Personal Workspace, a private folder that belongs to each user. Turn on Personal Workspaces for the users or groups that build workflows, and let them run personal automations. Personal workspaces describes how.

Studio Web has a few more tenant settings, such as the license model. Prerequisites for using Studio Web lists them.

Each plan includes a number of runs per month, and some users need a license for some features. Licensing for administrators has the numbers and the access table.

Your organization's governance settings apply to every Maestro Automate workflow from the first run, including policies, AI model governance, access control, and deployment approvals.

Orchestrator lists every deployed workflow, whichever tool deployed it. Builders follow, retry, and cancel runs in Maestro, so you need Orchestrator only for the tasks below.

The Deployments tab lists each deployment with its status, such as Active, its version, its last operation, and its stages. Select a deployment to open its panel, with Start job, Edit, Uninstall, and the Resources, History, and Jobs tabs.

A package that was published without being deployed, for example to the Orchestrator Tenant Feed from Studio Desktop, waits in Orchestrator:

To go back to an earlier version, open the Versions tab of the same panel, and select the deploy icon on the version's row.

Orchestrator lists each run as a job of the type Maestro Flow, under Automations > Jobs. A run that failed at a step shows as Running there until someone retries or cancels it in Maestro, because it's waiting.

To end a run from the list, select the ⋮ menu at the end of its row, then select one of these:

The same menu has Duplicate job, which starts a new run with the same inputs.

Each tenant runs up to 50 Maestro Automate runs at the same time. A run lasts up to 24 hours, and a run is kept for 30 days after it ends. Limits and fair use describes them.

A Maestro Automate run is kept for 30 days after it ends, and is then deleted. The work the run calls, the traces of that work, and audit events have their own retention settings:

These pages describe the other retention settings:

To keep a run's results, write them to an app or a Data Fabric entity before the run ends.

To keep traces and audit logs outside UiPath, an organization administrator can stream them to your own destination with Data Export. Data Export sends the data as it's produced, so the 30 days and the trace retention don't apply to the copy. The tenant needs Insights.

A workflow that answers or places phone calls needs a phone number connected to the tenant and bound to the deployed workflow. Deployment in the Agents guide describes how to set one up.