Skip to main content
Notifications keep your team informed about operational events without forcing them to live in the dashboard.

How it works

Notifications use the same event catalog as Webhooks — every batch, model-version, workspace, and API-key event in the catalog can be delivered as a notification. Where webhooks target your systems, notifications target your people.

Delivery channels

Each event can be delivered through:
  • Email — sent to the addresses of subscribed users
  • In-app — surfaced in the notification panel inside the dashboard
Channels are independent — you can enable email-only, in-app-only, or both per event subscription.

Configuring notifications

Notification preferences are configured per workspace from Settings → Workspace → Notifications. Each user can additionally manage their own subscription preferences and channel choices. The events you can subscribe to mirror the webhook event catalog — batches, model versions, workspace, and API keys.

Webhooks vs notifications

The two are complementary surfaces over the same underlying event stream:
NotificationsWebhooks
AudienceHumans on your teamYour systems
ChannelsEmail, in-appHTTPS callback
ConfigurationWorkspace + per-user preferencesPer endpoint, with signing secret
Use forAwareness, alerting on-call humansAutomation, pipeline triggers
Use notifications to keep your team informed. Use webhooks to drive automated pipelines. Both off the same canonical event catalog.