Notifications covers everything Authdog sends on your behalf: "Email events, providers, delivery channels, and templates for your application."
Two different things live here, and it helps to keep them apart:
- Email to your users — verification, invitations, magic links. Configured under Providers, Configuration, and Emails.
- Alerts to your team — audit and security events forwarded to Slack or a SIEM. Configured under Channels.
The rail also carries a RELATED block linking to Branding, Localization, and Domains.
Events
"Delivery, open, and bounce activity for emails sent from this application." A time-range selector (default: Last 30 days) sits in the header.
This is your deliverability view. Bounces concentrated on one domain usually mean a DNS or reputation problem at the receiving end; a flat zero when you expect traffic means the provider is not actually connected.
Providers
"Choose how emails are delivered. One provider is active at a time; the managed provider is used until you connect your own." Sub-tabs split Email from SMS.
| Provider | Setup |
|---|---|
| Authdog (managed) | Sends through Authdog's shared infrastructure. No setup required — the default. |
| Custom SMTP | Your own SMTP server: host, port, and credentials. |
| Resend | An API key from your Resend account. |
| SendGrid | A SendGrid API key, for high-volume sending. |
| Amazon SES | AWS access credentials and a region. |
| Postmark | Postmark server tokens. |
The active provider is marked In use; the rest show Connect.
Store provider credentials as environment secrets in Vault rather than pasting them into more than one place.
Configuration
"Defaults applied to every email sent from this application."
Sender identity — "The name and address recipients see in their inbox" — takes a From name, From address, and Reply-to address.
Delivery tracking — "Collect engagement metrics for emails sent from this application" — has two toggles:
| Toggle | Effect |
|---|---|
| Track opens | Inserts a tracking pixel to record when emails are opened. |
| Track clicks | Rewrites links to record when recipients click through. |
Both feed the Events tab. Both also have privacy implications — a tracking pixel is a third-party-style beacon in your users' inboxes — so enable them deliberately rather than by default.
Channels
"Configure where notifications are sent." Click "Add Channel" to create one; the table lists Name, Type, Default Channel, Recipients, Triggers, and Status.
Channels forward audit and security events to systems your team already watches:
| Type | Destination |
|---|---|
| Webhook | Any HTTPS endpoint you own. |
| Slack | A Slack channel via incoming webhook. |
| Datadog | Datadog Events API. |
| Sysdig | Sysdig Events API. |
| Splunk | Splunk HTTP Event Collector (HEC). |
| Sumo Logic | Sumo Logic collector. |
Each channel picks its triggers — which event types it cares about — so a Slack channel can carry only critical security signals while a SIEM channel takes everything.
Delivery is retried durably: a destination that is briefly unreachable does not lose events.
Emails
The template editor. Pick a template — Invitation, verification, magic link, and so on — and edit it with a rich-text editor. "Open preview" renders it, and each template has an enable toggle (for example "Send the invitation template when inviting a new user").
Per template you can set the Sender name, Reply-to email, and Subject, then compose the Email body with formatting controls (bold, italic, bullet list, heading, paragraph).
Variables
"Customize the selected template with reusable variables in {{VAR_NAME}} format." The Variables panel manages the tokens available in the editor and their preview values. Each has an Insert button that drops it at the cursor.
The invitation template ships with:
| Token | Resolves to |
|---|---|
{{USER_NAME}} |
The recipient's name |
{{APP_NAME}} |
Your application name |
{{INVITE_URL}} |
The accept-invitation link |
{{SENDER_NAME}} |
Who the invitation is from |
"Add variable" defines your own. "Reset draft" discards unsaved edits; "Save changes" publishes.
Related
| Read | To learn how to |
|---|---|
| Audit | Find the event types a channel can subscribe to |
| Lidar | Generate the security signals worth alerting on |
| Branding | Match email styling to the hosted pages |
| Vault | Store provider credentials as environment secrets |
| Events & webhooks | Consume forwarded events in your own systems |
| Email providers | Provider-specific setup details |