orchestrator
2023.10
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
- 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
Orchestrator user guide
Last updated Jul 1, 2025
Publishing an App to a Tenant
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.
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.
