Control how many notifications you receive per service with granular notification levels and review your notification history.

Notification Preferences

While alert rules define when notifications fire and channels define where they go, notification preferences let you control how much you hear about each individual service.

Notification levels

Every service you subscribe to has a notification level. The default level is ALL unless you change it.

Level	What you receive
ALL	Every status change — Degraded, Partial Outage, Major Outage, and recovery back to Operational.
MAJOR_ONLY	Only Partial Outage and Major Outage transitions (plus recovery). Minor degradations are suppressed.
OUTAGES_ONLY	Only Major Outage transitions and recovery. Partial outages and degradations are suppressed.
CRITICAL_ONLY	Only Major Outage when the severity is Critical (as defined by your alert rules). Recovery notifications are included.
NONE	No notifications for this service. The service still appears on your dashboard and its status is tracked — you simply are not alerted.

Use MAJOR_ONLY or OUTAGES_ONLY for services that frequently show brief degradations you do not need to act on. This keeps your inbox and Slack channel focused on real incidents.

Setting preferences for a service

From the service detail page

Open the service by clicking its name on the dashboard or in the service directory.
Click the Notifications tab.
Select a notification level from the dropdown.
Click Save.

From the settings page

Go to Dashboard → Settings → Notification Preferences.
You will see a table listing every service you subscribe to along with its current notification level.
Click the level dropdown next to any service and choose a new level.
Changes are saved automatically.

Notification preferences are per-user. If you are on a team, each member can set their own preferences independently.

Bulk editing preferences

To change the notification level for many services at once:

Go to Dashboard → Settings → Notification Preferences.
Use the checkboxes to select multiple services (or click Select All).
Click the Set Level button that appears above the table.
Choose the desired level from the dropdown.
Click Apply. All selected services are updated.

In-app notifications

PulsAPI includes an in-app notification popover accessible via the bell icon in the top navigation bar.

A red badge shows the count of unread notifications.
Click the bell to open the popover and see recent alerts.
Each notification shows the service name, new status, severity, and timestamp.
Click Mark as Read on individual items or Mark All as Read at the top.
Click a notification to navigate directly to the service detail page.

Notification history

The notification history log records every notification PulsAPI has attempted to deliver.

Accessing history

Navigate to Dashboard → Alerts → History.
The table shows all notifications sorted by most recent.

Understanding delivery states

State	Meaning
Sent	The notification was delivered successfully to the channel.
Pending	The notification is queued and waiting for delivery (usually resolves within seconds).
Failed	Delivery failed after all retry attempts. Hover over the status to see the error details.

Acknowledging notifications

You can acknowledge notifications to track which incidents your team has reviewed:

In the history table, click the Acknowledge button next to any notification.
The notification is marked with your name and a timestamp.
Use the Filter dropdown to show only unacknowledged notifications for triage.

Acknowledged notifications are visible to all team members, making it easy to see who has already reviewed an incident.

Filtering and searching history

Use the controls at the top of the history table to narrow results:

Filter	Options
Status	Sent, Pending, Failed
Channel	Email, Slack, Discord, Webhook
Service	Any subscribed service
Date range	Custom start and end date
Acknowledged	Yes / No

Notification Preferences

On this page