orchestrator

latest

false

Getting started
- Introduction
- Robots
- Auto Updating Client Components
- Time-to-live Periods
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
Cloud robots
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- Configuring an ExpressRoute connection
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
Orchestrator testing
- FAQ - Deprecating the testing module
  - FAQ - Migrating test artifacts to Test Manager
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide

DELIVERY:

Last updated Aug 4, 2025

Publishing an App to a Tenant

Apps in folders are always published to an Automation Cloud^TM Public Sector 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.
Click Publish.
Add a description for the new app version.
Click 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.

Once published, a new app version is created on the tenant.

You can check this information from the 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.

Storing deployed apps

App versions and deployed apps are physically stored within the same region as your Automation Cloud^TM Public Sector instance.

On this page

Publishing an App to a Tenant
Storing deployed apps

Was this page helpful?

PREVIOUSAbout Apps

NEXTManaging Apps

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2025 UiPath. All rights reserved.