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
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Orchestrator user guide
Last updated Feb 13, 2025
Using custom email settings
Customizing mail settings helps you tailor your email communication to precise specifications.
- Go to Admin, and from the top left corner, select Host (for host email settings), or your organization name (for organization-specific email settings). Then select Mail Settings. The Mail Settings page opens.
- Select the Use custom mail settings checkbox to set up your own server.
- Configure the custom email settings, by providing the neccessary information for your SMTP configuration.
- After entering the SMTP details, select Test mail settings to validate your settings. The Test mail settings page opens.
- Add an email address for sending the test email, and select Send. This sends a test email to a designated email address to ensure that your configuration is correct and functioning as expected. Make sure to check your inbox for the test email.
- Once the test email is successfully sent and received, select Save to save the SMTP settings. Custom email settings, when configured at the host level, apply to the host and all of its child organizations that do not have a custom configuration of their own. At the organization level, selecting custom settings allows you to implement a unique configuration that is specific to that particular organization. This configuration overrides any settings inherited from the host level, be they default or custom.
