- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
Publishing an App to a Tenant
Apps in folders are always published to an Automation Cloud Orchestrator tenant, similar to processes.
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.
- 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.
You can check this information from the Version history panel.
Storing deployed apps
App versions and deployed apps are physically stored within the same region as your Automation Cloud instance.