orchestrator
2023.4
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
 
- Audit
 - Settings - Tenant Level
 
 - Resource Catalog Service
 - Folders Context
 - Automations
 - Processes
 - Jobs
 - Triggers
 - Logs
 - Monitoring
 - Queues
 - Assets
 - Storage Buckets
 - Orchestrator testing
 - Other Configurations
 - Integrations
 - Classic Robots
 - Host administration
 - Organization administration
 - Troubleshooting
- About Troubleshooting
 - Alerts troubleshooting
 - General troubleshooting
 - Frequently Encountered Orchestrator Errors
 
 

Orchestrator user guide
Last updated Aug 26, 2025
Problem: Users do not receive configured alerts either in the user interface or via email when those alerts are configured for user groups with a SAML provisioning rule.
Solution: To resolve this issue, you can add affected users to the Administrators local group which allows them to receive alerts.
Warning: 
                  
                  
               
               
            Adding users to the Administrators group grants them with elevated privileges. Endeavor to understand the implications of these privileges. Ensure users are conferred administrator rights responsibly, maintaining a balance between the need for alerts access and preserving system security.