# Notifications and digests

Set what each person receives, without drowning anyone.

## What Naoshift sends

| Message | When | What it contains |
|---|---|---|
| **Daily digest** | Each morning, on days when there is something to say | New risks, changes, connector problems. Counts only |
| **Weekly digest** | Once a week, replacing the daily one that day | A short summary, the critical risks still open, the risks and changes of the week |
| **Monthly digest** | On the 1st of the month, replacing the other two that day | The same summary for the past month |
| **Incident alert** | As soon as a collection sees an outage, then its return | The name of the object: see [Incidents and subscriptions](/en/read/incidents-and-subscriptions) |

Digests **never name an asset**, only counts and types. A single e-mail goes out per morning.

## The steps

1. Each person opens **My notifications**, from their avatar menu at the top right, or under **Settings › My account**.
2. Each person ticks the digests they want, and saves.
3. An administrator opens **Settings › Organization › Company notifications**: the send time and the time zone of the company's digests.
4. If they wish, they connect a shared channel: **Slack**, **Microsoft Teams** or a webhook.
5. They test each address with **Test** before saving.

> These settings apply to the whole company; e-mail and SMS preferences stay individual.

## Three common-sense rules

- **An on-call alert does not go into a general channel**: point it at a channel your team really reads.
- **A Slack or Teams address contains a secret**: after a rotation, put it back here and run **Test** again.
- **Turning off e-mail does not turn off security**: sign-in codes always go out.

### A colleague receives no digest

It takes recent data: a live connector, or an import less than 30 days old. Then check their boxes in **My notifications**, and their spam folder. On a day with nothing to say, the daily digest does not go out.

### I get too many e-mails

Keep the weekly one, and turn off the daily one: the essentials are there. For incidents, set the kinds and the severity.
