Levelrail sends email for alert notifications (when an alert rule with an email channel fires), password-reset links and team invites. All of them go through one backend, configured once at Settings > Email.
Credentials are stored with the control plane’s envelope encryption, so a master key must be configured. They are never shown back after saving: a saved field reads “already configured, leave blank to keep it”.
Choose a backend
Works with any mail server or transactional provider that speaks SMTP (Gmail, Mailgun, Postmark, your own server). Needs a host, port, “from” address, and optionally a username and password.You can also set APP_SMTP_HOST, APP_SMTP_PORT, APP_SMTP_USERNAME, APP_SMTP_PASSWORD and APP_SMTP_FROM on the control plane. For installs already on AWS. Needs a region, access key ID, secret access key and a verified “from” address. A dedicated transactional provider with a single API key. Needs the API key and a “from” address. Configure it in Settings > Email or through PUT on the email settings API; the CLI’s settings email set covers SMTP and SES only.
levelrail-cli settings email get shows the current settings without credential values.
Test it
After saving, use Send test email in Settings > Email. It sends one real message through the same code path alerts, resets and invites use, so a successful test covers all three.
Other notification channels
Email is one channel among several. Slack, Discord, Telegram, PagerDuty and the rest are configured per channel at Settings > Notification channels. See Observability. Last modified on October 12, 2026
Get started
How-to guides
Reference
Concepts
Self-host gallery
Appendix