# Notifications

Source: https://getuptimely.com/docs/notifications

> Workspace channels, personal notification settings, and the in-app inbox.

Uptimely separates three notification surfaces, each with its own controls:
workspace channels (where the team coordinates), personal notifications
(what reaches you), and status-page subscribers (what reaches your
customers — see [Status pages](/status-pages)).

## Workspace channels [#workspace-channels]

Connect Slack and Discord under **Settings**, then decide per event family
what gets posted. Incident and alert lifecycles thread into the original
message, and posting is rule-gated — no rule, no post. Every delivery is
logged with an honest sent/failed status.

## Personal notifications [#personal-notifications]

Each user verifies their own contact methods — email, SMS, voice call — and
controls a per-event notification matrix under **User Settings →
Notification Settings**: which events reach them, on which channels. Push
notifications cover the web app and the iOS/Android apps.

On-call paging is separate and deliberate: escalation policies own paging
(see [On-call](/on-call)), and workspace-wide events never page devices.

## In-app inbox [#in-app-inbox]

The bell in the top bar is a real per-user inbox: team invitations,
incident and alert fan-out to project members, read/seen state synced
server-side across your devices.

## Delivery honesty [#delivery-honesty]

A notification Uptimely couldn't deliver is recorded as failed — counters
only increment on real deliveries, and failures surface loudly in logs
rather than disappearing.
