> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glood.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> The alert bell, Slack and email delivery, and the emails each member chooses to receive

An alert is Glood saying something in your stores needs a look. Alerts come from
two places: findings your agents record, and insights from the hourly checks.
Each one reaches you three ways: the bell in the dashboard, email, and Slack if
you connect it.

> [!NOTE]
>
> One problem, one alert. When a Store monitor agent explains an insight, you are
> alerted about its finding, which carries the cause, and not separately about the
> insight. See [Insights and agents](https://docs.glood.ai/platform/dashboard/insights.md#insights-and-agents).

## The bell

The bell sits in the top bar, with a count of the alerts you have not viewed.

* **New** holds what you have not viewed yet. **Earlier** holds what you have.
* Opening the bell marks nothing. Selecting an alert marks it viewed and opens
  the finding or insight behind it.
* **Mark all as read** clears New in one go. The bell lists the 50 newest unread
  alerts; if you have more, marking all as read clears the rest too.

Viewed is per person. Nothing you do in the bell changes what a colleague sees.

## Alert settings

Go to **Settings → Alerts**. Anyone can see this screen. Changing where alerts
go needs the `alert:manage` permission, and connecting Slack needs
`integration:write`. Without them the cards are read only.

### Email

Every organization has email alerts from the day it is created: switched on, and
sent to every member.

| Setting | What it does |
| - | - |
| **Email alerts** | On or off for the whole organization. One email per alert, sent as it is raised |
| **Send to: Every member** | Everyone who can see the alert's store, except members who switched alert emails off for themselves |
| **Send to: These addresses** | Exactly the addresses you list, members or not. Between 1 and 20, separated by commas |

Save changes with the save bar at the bottom of the screen. **Send test** sends
an alert email to you, so you can check it arrives and is not caught by a spam
filter.

To stop alert emails for the whole organization, switch **Email alerts** off and
save. To stop them for yourself only, see
[Your own email preferences](#your-own-email-preferences).

### Slack

**1. Connect Slack**

**Connect Slack** installs the Glood app in your Slack workspace. Approve it
in Slack and you come back here.

**2. Add a destination**

**Add destination**, pick a **Channel**, and optionally give it a **Name**
(it defaults to the channel's).

**3. Choose how long to hold alerts**

**Hold alerts for** groups the alerts raised inside the window into one
message: Immediately, 1 minute, 5 minutes (the default), 15 minutes or 1 hour.
Critical alerts ignore it and arrive at once.

**4. Send a test**

**Send test** on the destination posts a test message, and says what Slack
answered if it fails.

> [!TIP]
>
> For a private channel, invite the bot first: run `/invite @Glood` in that
> channel, then send a test.

**Remove** stops alerts going to that destination and changes nothing else.

If Slack rejects a message, the card shows **Needs reconnecting**. Choose
**Reconnect** to start alerts again. **Disconnect** stops all alerts reaching
Slack; your destinations are kept and come back if you reconnect.

### Recent deliveries

**Recent deliveries** lists what was sent, where, and whether it was **Sent**,
**Queued** or **Failed**. Look here first when someone says they did not get an
alert.

## Your own email preferences

Go to **Settings → Notifications**. These are yours alone, per organization: you
can mute one organization's email and keep another's. Each switch saves as soon
as you flip it.

| Group | What it covers |
| - | - |
| **Account and security** | Sign-in links, email verification, password resets and invitations. Required: these cannot be turned off |
| **Alerts** | Alerts raised by your agents, the system or a connected integration |
| **Reports** | Scheduled reports and digests for this organization |

Switching **Alerts** off removes you from **Every member** alert emails. It does
not remove an address listed under **These addresses**, and it does not change
the bell.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.