# Notifications

The **notification center** tells you when your orders and triggers do something worth knowing about, in the channels you choose. Open **Settings → Notifications** to pick which events fire on which channel, the **bell** at the top of the trading app to read the inbox, and a small **toast** in the bottom-right to catch live updates as they happen.

## The bell and the inbox

The bell in the top navigation shows the number of unread notifications. Click it to open the **inbox**: a feed of every notification, newest first, with the event, the symbol, the order or trigger it relates to, and the time. Order rows also show the trading style (Hybrid / Aggressive / Passive).

Each inbox row offers two actions:

- **Mark as read** / **Mark as unread**.
- **Dismiss notification** (the × at the end of the row) — removes it from the inbox.

**Mark all as read** at the top of the inbox clears every unread row in one go.

## Live toasts

Orders you place from the trading app show a short **toast** in the bottom-right when they are submitted, filled, cancelled or rejected, and when a trigger is created or fires. Toasts auto-dismiss after a few seconds. They do not depend on the **In-app** setting, and they do not appear for orders placed through the [public API](https://api-docs.anboto.xyz/).

## Settings

Open **Settings → Notifications** to control which events fire on which channel. Three channels are available — **In-app** (inbox and toast), **Email**, **Telegram** — and a Slack integration is offered as an additional destination. Each is on or off per event.

!!! note "Defaults"
    By default every channel is **off** for every event — opt in to the events and channels you want. Live toasts for orders you place in the app are not affected by these settings.

The settings screen groups events into three matrices:

- **Trading** — order submitted, order filled, order cancelled, order rejected.
- **Triggers** — trigger created, trigger enabled, trigger disabled, trigger fired.
- **News & updates** — Anboto changelog and product updates.

**Telegram** messages go to your team's Telegram group. A team admin connects the group from **Settings → Notifications**: generate a code, then send it in the group with `/start`. Once bound, Telegram shows as connected. To remove the group, an admin clicks **Disconnect Telegram group?** and confirms (**This team will stop receiving Telegram notifications.**).

The **API-order** toggle (under **Trading**) controls whether orders placed through the [public API](https://api-docs.anboto.xyz/) fire notifications the same way as orders placed from the app. Turn it off to silence API-only flow.

A **Sound** switch at the top of the settings plays a chime when a fill arrives in the inbox (separate from the toast sound).

## Admin overrides

Team admins can **force** or **mute** an event for the team's members from **Settings → Notifications** — useful to make sure everyone receives fills, or to silence a noisy event. A force overrides your user preference (the notification always fires); a mute suppresses it (the notification never fires). The order of precedence is **admin force/mute → user preference**, so a user opting in to an event still receives nothing if an admin has muted it, and a user opting out still receives a force.

## See also

- [Settings overview](../setup/teams-and-accounts.md) — the **Settings** menu the Notifications screen lives under.
- [Triggers](../order-types/triggers.md) — the events in the **Triggers** matrix are fired by trigger orders, armed from the order form with **+ Trigger**.
- [Managing orders](../reference/managing-orders.md) — the **order submitted / filled / cancelled / rejected** events match the order statuses explained there.