- 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
Using default email settings
Default email settings are preconfigured parameters provided by UiPath for sending system email notifications. Default settings use the SendGrid SMTP server and are designed to work out of the box, requiring no additional customization.
When selected at the host level, the default UiPath email settings apply to the host and all of its subordinated organizations. The host can also have custom email settings.
Whatever configuration - default or custom - that is set at the host level, it propagates down to all child organizations that did not customize their own email settings. Organization custom settings override the inherited settings from the host.
When the default mail settings are chosen at the organization level, settings from the host level - either the standard UiPath or any custom host configurations - are adopted. Nevertheless, these settings can be overridden at the organization level with custom configurations.