Skip to main content

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:

In-app

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.

Email

The same events delivered to your inbox, so you stay informed even when you’re not signed in.
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.
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.

Notification types

MagOneAI raises notifications across several categories. The names below are the plain-English events behind each alert.
CategoryYou’re notified when…
MembershipYou’re invited to an organization · your role changes · a new member joins
WorkflowsA use case is created, updated, or deleted · a schedule is changed · a schedule fails
ExecutionsAn execution completes, fails, or is cancelled · a long-running execution finishes · a scheduled run fails · an API-triggered run fails
SecurityThe 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 & filesA token-usage threshold is reached · a high failure rate is detected · a file extraction finishes
Execution and schedule notifications pair naturally with Triggers & execution — a “scheduled run failed” alert is your cue to open the execution history and drill into what went wrong.

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.
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 for where platform-wide settings live.

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.
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.

Keeping notifications tidy

Two behaviors keep your notification center useful instead of noisy:

De-duplication

The same event won’t notify you over and over. Notifications are de-duplicated, so a single happening produces a single alert.

Automatic cleanup

Read notifications are cleaned up automatically after 90 days, so your history stays current without manual housekeeping.

Notifications vs. audit logging

Notifications and audit logs both surface activity, but they serve different purposes — and you’ll want both.
NotificationsAudit logging
PurposeReal-time alerts that something happenedThe permanent, authoritative record of what happened
LifespanRead alerts cleaned up after 90 daysRetained as the system of record
Best forReacting quickly to events as they occurInvestigations, compliance, and after-the-fact review
A security notification (for example, “new login detected”) is an alert meant to prompt action. The corresponding entry in the audit log is the durable record you rely on for compliance and investigation.

Next steps

Admin Portal

Where platform admins configure org-wide notification defaults and security policies

Triggers & execution

Understand the execution and schedule events behind your alerts

Audit logging

The permanent record of activity, distinct from real-time notifications