orchestrator
latest
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Sep 17, 2025
Publishing an App to a Tenant
linkApps in folders are always published to an Automation CloudTM Orchestrator tenant, similar to processes.
Before publishing an app to a tenant, make sure that you have the right permissions.
To publish an app to a tenant, the Create permission under App Versions is needed. If you are part of a default group, such as administrator or Automation user, this permission is granted automatically. You can also create a custom role to grant this permission.
- Depending on the app type:
-
For classic apps, go to UiPath Apps.
-
For web apps, go to Studio Web.
-
- Open the app you want to publish to Orchestrator.
- Select Publish.
- Add a description for the new app version.
-
Select Publish.
Note: The tenant field is filled in automatically with one of the following:
- The tenant your app is connected to.
- If your app has no tenant integration, the active tenant from the top-right navigation bar.
Figure 1. Publishing a new app version
Once published, a new app version is created on the tenant.
You can check this information from the Version history panel.
Figure 2. Version history panel
Note: If your app was previously published in a non-tenant context (before the Apps in Folders feature was released), a warning
message pops up when you first try to publish the app to a tenant.
Figure 3. Warning message
Storing deployed apps
linkApp versions and deployed apps are physically stored within the same region as your Automation CloudTM instance.