Sending email through your own SMTP
Have the workspace's email sent from your own mail server.
Settings → SMTP
Routes this workspace's notification email through your own mail server — an alternative to the API-key based providers under Settings → Notification channels. Owner/Admin only.
When to use this instead of Notification Channels
If your org already has SendGrid, Mailgun, or Resend, use Notification Channels — it's simpler and doesn't need a mail server. Use SMTP here if you want to send through your own Exchange, Postfix, or other mail relay instead of a third-party API.
How it's chosen
- An enabled email provider under Notification Channels is tried first for notification email.
- Otherwise, SMTP enabled and fully configured here → used next. It is also the only route that can carry attachments.
- No SMTP, or your server rejects the send → falls back to the platform's built-in email provider, if your plan includes it.
- None of these available → notification email is silently skipped.
Password storage
The password is encrypted before it's stored — this page never shows it back to you, only the last 4 characters, so you can confirm which credential is active without re-entering it every time you change another field.
Always Send test after saving, before relying on this in production — a wrong port or TLS setting fails silently for real notification email (nobody sees an error — the mail goes out another way or never arrives), but the test button reports the real connection error immediately.