> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/technical-docs/notification-center/email-notifications.md).

# Email Notifications

Daasity emails you when something needs attention, once per problem rather than every time it repeats.

### Who receives emails

Any active user on your account with email notifications turned on. The Notifications page shows how many people are receiving them ("Emailing 3 people").

If no one is set to receive emails, the bell shows an orange dot and a **Choose recipients** prompt.

### Turn on email notifications for a user

1. Go to **Account** > **Users**.
2. Edit the user.
3. Turn on the email notifications toggle.
4. Click **Save**.

### When emails are sent

| Notification                                                                                              | Email                                                                                                                                                                      |
| --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ongoing problems (Reconnect needed, Couldn't reach the source, Sheet didn't load, YML Definition Changed) | Once, when the problem first appears. Repeats update the notification in the app without another email.                                                                    |
| Vendor issue                                                                                              | Never. Daasity is handling it, so it shows in the app only.                                                                                                                |
| Backfill didn't finish                                                                                    | Never. Shows in the app only.                                                                                                                                              |
| File couldn't be loaded, Integration paused, TikTok Report Field Changed                                  | Each time.                                                                                                                                                                 |
| Report Quota Exceeded, Report Stalled at Source                                                           | At most once per integration per day.                                                                                                                                      |
| Some data was skipped                                                                                     | At most once per day for each data refresh. No email is sent when everything skipped was caused by a login problem, because that problem already has its own notification. |
| Reports may be stale                                                                                      | Only if you manage your own transformation code.                                                                                                                           |

If a problem is fixed and later comes back, it counts as a new problem and sends a new email.

Integrations that haven't refreshed successfully in more than 90 days still show notifications in the app, but don't send emails.

### What the email includes

The same plain-language message you see in the app, the error details when available, and a **View notification** button that takes you to it.