- 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
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Automation Suite 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
- Storage Buckets
- Orchestrator testing
- Integrations
- Troubleshooting
Publish an app from a folder to an Orchestrator tenant, including required permissions and publishing steps.
Apps in folders are always published to an Automation Suite 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 permssion 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.
-
Go to UiPath Apps.
-
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.
Once published, a new app version is created on the tenant.
You can check this information from the Version history panel.
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 Suite instance.