# Baserow Notifications: In-App Panel and Email Digest Setup

> Collaborator assignments, workspace invites, and webhook failures reach you two ways in Baserow - via the in-app panel or a tunable email digest.

Source: https://opennix.org/en/docs/baserow/account/notifications/


Baserow surfaces workspace activity through two channels - an in-app notifications panel and email, with a frequency you can dial from instant to fully off - this article covers what triggers each one and how the email digest is built.

## What triggers a notification

Notifications remove the need to keep checking a workspace manually - Baserow flags the events that matter on its own. In the open-source edition, notifications fire for:

- **Workspace invitations** - when you're invited to join a workspace.
- **Collaborator assignments** - when someone adds you as a collaborator on a specific row via the Collaborator field.
- **Form submissions** - when someone submits a form you own (enabled per form).
- **Integration failures** - when a webhook stops delivering after repeated failed attempts.
- **Product updates** - when a new Baserow version releases (optional).

## The in-app notifications panel

In-app notifications appear inside the Baserow interface and stay in the panel until you read or clear them.

![Notifications panel in Baserow](/images/baserow/account/notifications-panel.png)

### Opening the panel

1. Click **Notifications** in the sidebar.
2. A modal opens listing every notification in chronological order.
3. Unread notifications show a blue dot, a distinct background, and a badge count on the Notifications tab.

### Working with notifications

Clicking any notification jumps straight to what it's about - the row, the workspace invitation, or the form response.

- **Mark all as read** clears the unread indicator from every notification at once.
- **Clear all** permanently removes every notification from the panel.

Unread notifications stay visible until they're read or cleared manually, and the Notifications tab badge always reflects the current unread count.

## Email notifications

Email notifications land in the address tied to your Baserow account and mirror a subset of what shows up in the panel - useful when you're not in Baserow constantly.

![Baserow email notification settings](/images/baserow/account/notifications-email-settings.png)

### Setting the frequency

1. Click the workspace icon in the top-right corner.
2. Select **Settings**.
3. Open the **Email notifications** tab.
4. Pick a frequency:

| Frequency | Behavior |
|---|---|
| **Instantly** | A separate email fires right after each event |
| **Daily** | One digest email at midnight UTC |
| **Weekly** | One digest email once a week |
| **Never** | No emails sent, notifications stay in-app only |

A digest bundles up to 10 notifications into a single email; past that, the email shows a "Plus X more notifications" line with the remaining count. Daily digests go out at midnight UTC - self-hosted instances can adjust that time and day in instance settings.

### What sends an email

An email fires when:

- you're invited to join a workspace;
- you're added as a collaborator on a row through the [Collaborator field](/docs/baserow/field-types/collaborator-field/);
- someone submits a form that has notifications turned on;
- a [webhook](/docs/baserow/webhook-api/webhooks/) stops delivering data and gets deactivated.

## Form submission notifications

A form submission notification only arrives when the form's owner has explicitly turned it on for that specific [form](/docs/baserow/view-types/guide-to-creating-forms-in-baserow/) - it's off by default.

![Form submission notification toggle in Baserow](/images/baserow/account/notifications-form-submission-settings.png)

To turn it on:

1. Open the form in edit mode.
2. Scroll to the bottom of the form editor.
3. Toggle **"Receive form notifications"** on.

Useful for customer feedback forms, lead capture, or event registrations - anywhere a fast reaction to a new response matters.

## Webhook failure notifications

System notifications flag a broken integration early, before it silently disrupts a workflow:

- **Webhook failure.** A notification arrives after four consecutive failed delivery attempts, at which point the webhook deactivates automatically.
- **Payload size limit.** A notification arrives when a webhook can't deliver the full payload because of the size limit; Baserow sends a partial payload (the first 1,000 records) and the notification flags the truncation.

See [Baserow Webhooks](/docs/baserow/webhook-api/webhooks/) for how to configure webhooks themselves and which events they react to.

## Frequently asked questions

**Why am I not getting email notifications?** Work through these in order: frequency is set to Never (switch to Instantly, Daily, or Weekly under Settings → Email notifications); the emails are landing in spam (mark Baserow's messages as not spam); the account email on file is wrong (check it in account settings); a self-hosted instance has no SMTP configured (ask the instance administrator).

**Can I turn off notifications for just one workspace?** Not directly - the email frequency setting applies globally across every workspace. To cut down on notifications from one workspace, turn off notifications on the forms in that workspace you don't need to monitor.

**What happens to notifications when I leave a workspace?** New notifications about that workspace stop immediately. Notifications you already received stay in the panel until cleared manually.

**Can a workspace admin control my notification settings?** No. Notification preferences are personal account settings that only the account owner controls - a workspace admin can't change someone else's email frequency or turn on notifications for someone else's forms.

**Do notifications work on mobile?** In-app notifications work in a mobile browser when Baserow is open. Email notifications reach any device with mail access. Baserow has no dedicated mobile app with native push notifications.

**How long are notifications kept?** In-app notifications persist indefinitely until cleared by hand. Email notifications follow your own mail provider's retention rules; on self-hosted instances, very old records may get archived as part of routine database maintenance.