# Notifications

Source: https://docs.tightly.io/help/settings/notifications
Reviewed: 2026-09-07

## The question this page answers

Which events email me, and where do they go? Notifications is yours: it decides what reaches your own address. In-app notifications are on by default for every event but the daily digest, which has no in-app version, and the page draws no switch for them. Slack is the organisation's and is set on Integrations.

## What you see

The head is the page's name; like every Settings page it carries no sentence.

One table of five rows: **Event** (`Inventory`, `Purchase orders`, `Budget`, `System`, `Daily digest`) and **Email**, a switch per row. A **Slack** column is drawn only when the organisation's Slack connection posts some events and not others, each cell a mark read as `Posting` or `Not posting`, read and never pressed; where every row would say the same the column leaves and the fact is said once, in the Slack row beside the table.

**Where they go** holds two rows. Email is your own address from your account, or `No address on file`. Slack is the connection's state, `Not connected`, `Connected`, `Connected, posting all 5 events` or `Connected, posting nothing yet`, with the door Integrations; while it reads it says `Checking the Slack connection`, and a failed read `The Slack connection did not load`.

## What each event covers

**Inventory** is stock: a stock-out, low stock, overstock, a bundle that cannot be built, and an event whose demand is not covered. **Purchase orders** is an order's life: a new supplier email, a delivery created, a status change, a delivery date, an overdue order and a supplier's signal about a date, a status or a quantity. **Budget** is money: a budget exceeded or near its limit, a fiscal year starting or approaching, open to buy over its envelope and an increase approved or declined, and on Tightly Pro a commitment breaching its verdict, waiting on a signature or carrying a proposed amendment. **System** is the platform: an import finished or failed, a sync finished, an integration issue, a sold-units limit, a skill step waiting on you, a mention in a comment, planned maintenance and the onboarding nudges. **Daily digest** is the digest itself.

## What to do

Press a switch; the change writes on its own and reads back in the cell. There is no Save. The switch saves your own preferences, and saving them needs the Member rung: a Viewer who presses one is answered

> Your access level does not cover this. Ask an admin on Team to raise it.

To change which events post to Slack, or to connect Slack at all, open Integrations and the Slack connector page; that is the organisation's decision, not a person's, so it does not live here.

## When it is empty or failed

The five rows are always drawn, so there is no empty state. A Slack read that failed says so in the Slack row, `The Slack connection did not load`, and the column stays away. A switch the server refused prints the server's sentence under the table, or "The change was not saved and no reason came back." where none came.