# Administration

> 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.

## 1. Turn on the services

Turn on these services for the tenant. [Managing services](/automation-cloud/automation-cloud/latest/admin-guide/managing-services) describes how.

| Service | What workflows use it for |
|---|---|
| Orchestrator | Runs deployed workflows and stores their runs. Required. |
| Integration Service | The connections to other apps, such as Slack or Gmail. |
| Action Center | Human steps, such as approvals and escalations. |
| Data Fabric | Data entities that workflows read and write. |
| Document Understanding and Intelligent Xtraction and Processing (IXP) | Nodes that read and extract data from documents. |

Insights isn't required.

## 2. Turn on Personal Workspaces

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](/orchestrator/automation-cloud/latest/user-guide/personal-workspaces) describes how.

Studio Web has a few more tenant settings, such as the license model. [Prerequisites for using Studio Web](/studio-web/automation-cloud/latest/user-guide/prerequisites-for-using-studio-web) lists them.

## 3. Check licensing

Each plan includes a number of runs per month, and some users need a license for some features. [Licensing for administrators](licensing-for-administrators.md) has the numbers and the access table.

## Governance

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.

- [Governance](/automation-ops/automation-cloud/latest/user-guide/governance-intro) in Automation Ops describes the policies you can set.
- [About AI Trust Layer](/automation-cloud/automation-cloud/latest/admin-guide/about-ai-trust-layer) describes how to govern the AI models that agents use.

## Deployments in Orchestrator

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.

### Manage deployments

1. In Orchestrator, select the **Solutions** tab.
2. In the left panel, select the folder the workflow is deployed to, such as a user's **My Workspace** or a shared folder.

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.

### Deploy a published package

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

1. In Orchestrator, select **Tenant** at the top of the left panel.
2. Select **Solutions**, then the **Packages** tab. Each solution is listed with its latest version.
3. Select the solution. Its panel opens.
4. Select **Deploy**.

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.

### Runs as jobs

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:

- **Stop** ends the run. Its status changes to **Stopped**.
- **Kill** forces the run to end right away. Its status shows **Terminating**, then **Stopped**.

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

## Limits

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](limits-and-fair-use.md) describes them.

## How long run data is kept

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:

| Data | Where you see it | How long it's kept |
|---|---|---|
| The run | **Instance management** in Maestro, and the job of the run in Orchestrator, with its logs | 30 days after the run ends. Then it's deleted. |
| Work the run calls | The jobs of the agents, RPA workflows, and other automations that the run starts | Their own retention settings. The 30 days don't apply to them. |
| Traces of the work the run calls | The traces of agents and other automations | 90 days by default. An administrator can shorten it to 1 or 7 days. |
| Audit events | Automation Cloud audit logs | Captured the same way in Maestro Automate and Maestro Orchestrate. |

These pages describe the other retention settings:

- [Time-To-Live enforcement for Trace data](/automation-ops/automation-cloud/latest/user-guide/settings-for-ai-trust-layer-policies#time-to-live-enforcement-for-trace-data) in the Automation Ops guide: the AI Trust Layer policy setting that sets how long traces are kept, 90 days by default.
- [Process data retention policy](/orchestrator/automation-cloud/latest/user-guide/process-data-retention-policy) in Orchestrator: how long the jobs of other automations are kept.
- [Retention periods](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/about-logs#retention-periods) in the Automation Cloud admin guide: how long audit logs are kept.

### Keep a copy for longer

To keep a run's results, write them to an app or a [Data Fabric entity](data-fabric-entity-nodes.md) 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](/automation-cloud/automation-cloud/latest/admin-guide/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.

## Phone numbers for voice workflows

A workflow that answers or places phone calls needs a phone number connected to the tenant and bound to the deployed workflow. [Deployment](/agents/automation-cloud/latest/user-guide/conversational-agents-voice-deployment) in the Agents guide describes how to set one up.

## Next steps

- [Licensing for administrators](licensing-for-administrators.md): included runs, what's billed separately, and user access.
- [Troubleshooting](troubleshooting.md): problems that builders bring to you.
- [System requirements](https://docs.uipath.com/overview/other/latest/overview/cloud-software-requirements): supported browsers and computers.
- [Community](community.md): ask questions and share workflows with other builders on the UiPath Forum.