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
- Settings
- 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
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Nov 4, 2024
Running a Deployed App from a Folder
Once an app is deployed in a folder, you
can run it from here or from the Apps home page.
Before running an app from a folder, make sure that the following prerequisites are met:
- The app is already deployed in the folder.
- You have the rights permissions. To run an app from a folder, the View permssion under Apps 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.
The app is opened in UiPath Apps.
