---
title: Notifications
description: Email and in-app alerts for the events that matter to your team — driven by the same event catalog as webhooks.
---

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](/pt-BR/integrate/webhook-notifications)** — 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](/pt-BR/integrate/webhook-notifications#event-catalog) — batches, model versions, workspace, and API keys.

## Webhooks vs notifications

The two are complementary surfaces over the same underlying event stream:

| | Notifications | Webhooks |
|---|---|---|
| **Audience** | Humans on your team | Your systems |
| **Channels** | Email, in-app | HTTPS callback |
| **Configuration** | Workspace + per-user preferences | Per endpoint, with signing secret |
| **Use for** | Awareness, alerting on-call humans | Automation, pipeline triggers |

Use notifications to keep your team informed. Use webhooks to drive automated pipelines. Both off the same canonical event catalog.