Notification channels
A channel is a way to deliver an alert. UnitOps supports six kinds, each with a provider you choose per organization.
Page: Admin -> Channels (/admin/channels) · Role required: admin
| Channel | Providers | Notes |
|---|---|---|
| In-app | Built in | Always available; drives the bell and the notification page |
| SMTP, AWS SES, SendGrid, Postmark | Pick one per organization | |
| Web push | Web Push | Browser and mobile push after the user allows notifications |
| Slack | Slack App (OAuth install) | Channel posts, per-user DMs, and AI chat, see Connect Slack |
| Microsoft Teams | Teams Bot (multi-workspace) | Bot Framework delivery with Adaptive Cards: channel posts, per-user DMs, and AI chat across tenants |
| SMS | Twilio, AWS SNS | Currently in beta and locked in the UI |
A development-only Console provider, which writes the rendered message to disk instead of sending it, backs each channel on local and staging environments. It is not offered in the provider dropdown, so admins pick from the real providers above.
How to configure a channel
- Go to Admin -> Channels.
- Find the card for the channel kind.
- Choose the provider.
- Fill in the provider fields (below).
- Click Save.
- Click Send test message to default channel and confirm it arrives.
Secrets can be entered directly or given as a vault reference such as vault://kv/smtp-password, which keeps the value out of the database.
Email
AWS SES
| Field | Example |
|---|---|
| AWS Region | us-east-1 |
| From address | alerts@yourcompany.com |
| Reply-to address | ops@yourcompany.com |
The sending identity must be verified in SES, and the account must be out of the SES sandbox to email unverified recipients.
SMTP
| Field | Example |
|---|---|
| SMTP host | smtp.gmail.com |
| Port | 587 |
| Username | alerts@yourcompany.com |
| Password | vault://kv/smtp-password |
| From address | alerts@yourcompany.com |
Postmark
Provide the server API token (or vault://kv/postmark-token) and the verified From address.
Web push
- Enable the push channel in Admin -> Channels.
- Each user opens Settings -> Notifications, expands Channels & devices, and clicks Enable push.
- The browser prompts for permission; the device then appears in the user's device list.
Push requires HTTPS, so it works on both the production and staging domains but not on a plain HTTP local host.
SendGrid
Provide the SendGrid API key (or vault://kv/sendgrid-api-key) with Mail Send permission and the verified From address.
Microsoft Teams
Teams uses a single Teams Bot (Multi-workspace) provider built on the Bot Framework, which delivers Adaptive Cards to channels, sends per-user DMs, and powers AI chat across multiple tenants.
- On the Teams card, click Add to Teams and complete the connect flow.
- The connected workspace then appears under Workspaces; configure its channels there.
Platform admins also have an advanced option to manually register a tenant-owned Azure AD app. See Connect Microsoft Teams for the full walkthrough.
SMS
SMS is currently in beta and locked in the UI, so its providers cannot be configured yet. When it opens up, Twilio (account SID, auth token, and From number) and AWS SNS (region, using the API's IAM credentials) are the planned providers.
Per-organization overrides
Channel configuration is stored per organization, so one tenant can send email through SES while another uses SendGrid. Each admin only sees their own organization's configuration.
Test and verify
Every card has Send test message to default channel. If the test fails, the error text names the provider response; fix the credential or destination and retry. Deliveries that fail repeatedly land in the dead-letter queue on the Delivery Health tab, see Notifications overview.