> ## Documentation Index
> Fetch the complete documentation index at: https://pulse-41cf5b0d.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Manage Status Page Subscribers and Notifications
> Let visitors subscribe to your status page for email notifications on incidents, maintenance, and recovery — with per-monitor subscription options.
Subscribers are visitors who opt in to receive email notifications whenever the status of your services changes. PulseGuard's subscription system uses a double opt-in flow to verify email addresses, lets subscribers choose exactly which monitors they care about, and automatically sends updates throughout the full incident lifecycle — from the moment an issue is detected through to resolution. You can also share RSS and Atom feed URLs with users who prefer feed readers over email.
## How subscriber notifications work
A **Subscribe** button appears on every public status page. When a visitor clicks it, they enter their email address and are sent a verification email. They must click the confirmation link in that email before they are added to your subscriber list. This double opt-in flow prevents spam subscriptions and ensures your notification emails reach genuinely interested recipients.
Once verified, the subscriber begins receiving notifications for the monitors they selected. You can view and manage all subscribers from the dashboard.
## Email verification flow
The visitor clicks **Subscribe** on your status page, types their email address into the subscription form, and clicks **Subscribe**.
PulseGuard sends a verification email to the address provided. The email contains a unique confirmation link that expires after 24 hours.
The visitor clicks the confirmation link in their inbox. PulseGuard marks the email as verified and activates the subscription.
From this point on, the subscriber receives email alerts for the monitors they chose whenever an incident is created, updated, or resolved.
If a visitor does not confirm their subscription within 24 hours, the pending entry is automatically removed. The visitor can subscribe again at any time.
## Per-monitor subscriptions
When subscribing, visitors can choose which monitors they want to follow rather than receiving notifications for every monitor on the page. This is particularly useful for large status pages with many services — a customer who only uses your API can subscribe to the API monitor without receiving alerts about your marketing website.
Subscribers can update their monitor preferences at any time by clicking the **Manage Subscription** link included in every notification email.
## What subscribers receive
PulseGuard sends email notifications at each stage of an incident's lifecycle:
| Notification type | Trigger |
| ------------------------- | ------------------------------------------------------------------------- |
| **Incident opened** | A monitor the subscriber follows transitions to a down or degraded state. |
| **Status update** | An incident moves through `Investigating` → `Identified` → `Monitoring`. |
| **Maintenance announced** | A maintenance window is scheduled that affects a monitored service. |
| **Maintenance started** | A scheduled maintenance window begins. |
| **Maintenance ended** | A maintenance window concludes and monitors resume normal checking. |
| **Incident resolved** | A monitor recovers and the incident is marked as resolved. |
## Manage subscribers from the dashboard
Go to **Dashboard → Pages → your page → Subscribers** to view and manage your subscriber list. From this view you can:
* **Search** subscribers by email address.
* **Remove** individual subscribers — useful if a user reports receiving unwanted emails.
* **Export** the full subscriber list as a CSV file for CRM integrations or audits.
Removing a subscriber from the dashboard immediately unsubscribes them. This action cannot be undone — if the subscriber wants to rejoin, they must go through the opt-in flow again.
## RSS and Atom feeds
In addition to email notifications, every status page exposes RSS and Atom feeds that users can add to any feed reader application. Feeds update within 5 minutes of a new incident or event.
| Endpoint | Description |
| ------------------------------- | --------------------------------------------------------------- |
| `GET /api/feeds/:slug/rss` | RSS feed of the 50 most recent incidents from the last 90 days |
| `GET /api/feeds/:slug/rss-all` | RSS feed of all recorded events |
| `GET /api/feeds/:slug/atom` | Atom feed of the 50 most recent incidents from the last 90 days |
| `GET /api/feeds/:slug/atom-all` | Atom feed of all recorded events |
Each feed item includes the incident title, affected monitor name, current status, description, and the time of last update.
Share the RSS feed URL directly on your status page or in your documentation. Power users and engineering teams often prefer feed readers like Feedly, Inoreader, or self-hosted RSS aggregators over email, since feeds can be integrated into Slack, Microsoft Teams, or custom alerting pipelines without writing any code.
## Notification deliverability
PulseGuard sends subscriber emails through a dedicated transactional email provider. To maximise deliverability:
* **Add SPF and DKIM records** for your sending domain to authenticate outbound email and reduce the chance of notifications landing in spam.
* **Use a custom sending domain** (e.g., `notifications@status.yourcompany.com`) so emails appear to come from your brand rather than a generic PulseGuard address.
* **Encourage subscribers to whitelist** your notification address if they use aggressive spam filters.
Currently, subscribers receive notifications immediately when a trigger event occurs. Digest or batched notification modes are on the roadmap for a future release.
Subscriber limits depend on your plan tier. Check **Settings → Billing** in the dashboard to see the limit for your current plan.
Bulk import is not available in the UI today. You can use the PulseGuard API to programmatically add pre-verified subscribers. See the API reference for the `POST /api/pages/:slug/subscribers` endpoint.