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

# Notifications

> Stay on top of what happens in your organization — in-app alerts and email for the events that matter

## How notifications work

MagOneAI keeps you informed about the things you care about — a new invitation, a workflow that finished, a failed schedule, a sign-in from a new device — without making you go looking for them. Notifications are delivered over two channels:

<CardGroup cols={2}>
  <Card title="In-app" icon="bell">
    A notification center in the platform with an unread badge. New notifications arrive in real time — they stream in live, with no page refresh needed.
  </Card>

  <Card title="Email" icon="envelope">
    The same events delivered to your inbox, so you stay informed even when you're not signed in.
  </Card>
</CardGroup>

Which channel an event uses depends on its notification type and the org-wide defaults your platform admin has set.

## The notification center

The in-app notification center is where every alert lands. From it you can:

* **See unread alerts at a glance** — an unread badge shows how many notifications you haven't viewed yet.
* **Mark a notification as read** — clear it from your unread count once you've seen it.
* **Mark all as read** — clear the whole unread count in one action when you've caught up.

<Note>
  New notifications appear live. Because they stream in real time, you'll see an alert the moment its event happens — you don't need to reload the page to find it.
</Note>

## Notification types

MagOneAI raises notifications across several categories. The names below are the plain-English events behind each alert.

| Category          | You're notified when…                                                                                                                                                                                                          |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Membership**    | You're invited to an organization · your role changes · a new member joins                                                                                                                                                     |
| **Workflows**     | A schedule is changed · a schedule fails                                                                                                                                                                                       |
| **Executions**    | An execution completes, fails, or is cancelled · a long-running execution finishes · a scheduled run fails · an API-triggered run fails                                                                                        |
| **Security**      | The superadmin changes · your account status changes · your password changes · a new login is detected · an API key changes · an OAuth or tool connection token expires · an MCP tool server goes offline or comes back online |
| **Usage & files** | A token-usage threshold is reached · a file extraction finishes                                                                                                                                                                |

<Tip>
  Execution and schedule notifications pair naturally with [Triggers & execution](/workflows/triggers-and-execution) — a "scheduled run failed" alert is your cue to open the execution history and drill into what went wrong.
</Tip>

## Choosing channels per type

Each notification type has a default delivery channel — some events go to both email and in-app, others are in-app only. Sensible defaults ship out of the box, so you don't have to configure anything to start receiving the important alerts.

<Note>
  **Admin-only.** Platform admins set the org-wide default channel(s) for each notification type from the Admin Portal. For example, a critical security event might default to email + in-app, while a routine update is in-app only. See [Admin Portal](/platform/admin-portal) for where platform-wide settings live.
</Note>

## Email delivery

Email notifications are sent through your deployment's configured email provider. MagOneAI works with common providers — SendGrid, Resend, Gmail (API / OAuth), and standard SMTP — so the same alerts reach your inbox regardless of the underlying setup.

<Note>
  **Admin / infrastructure concern.** The email provider is chosen once for the deployment by your platform or IT team. As a user, you don't pick a provider — you simply receive the emails for the types configured to use email.
</Note>

## Keeping notifications tidy

Two behaviors keep your notification center useful instead of noisy:

<CardGroup cols={2}>
  <Card title="De-duplication" icon="layer-group">
    The same event won't notify you over and over. Notifications are de-duplicated, so a single happening produces a single alert.
  </Card>

  <Card title="Automatic cleanup" icon="broom">
    Read notifications are cleaned up automatically after 90 days, so your history stays current without manual housekeeping.
  </Card>
</CardGroup>

## Notifications vs. audit logging

Notifications and audit logs both surface activity, but they serve different purposes — and you'll want both.

|              | Notifications                            | Audit logging                                         |
| ------------ | ---------------------------------------- | ----------------------------------------------------- |
| **Purpose**  | Real-time alerts that something happened | The permanent, authoritative record of what happened  |
| **Lifespan** | Read alerts cleaned up after 90 days     | Retained as the system of record                      |
| **Best for** | Reacting quickly to events as they occur | Investigations, compliance, and after-the-fact review |

<Note>
  A security notification (for example, "new login detected") is an alert meant to prompt action. The corresponding entry in the [audit log](/security/audit-logging) is the durable record you rely on for compliance and investigation.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Admin Portal" icon="gear" href="/platform/admin-portal">
    Where platform admins configure org-wide notification defaults and security policies
  </Card>

  <Card title="Triggers & execution" icon="play" href="/workflows/triggers-and-execution">
    Understand the execution and schedule events behind your alerts
  </Card>

  <Card title="Audit logging" icon="clipboard-list" href="/security/audit-logging">
    The permanent record of activity, distinct from real-time notifications
  </Card>
</CardGroup>