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

# Subscription management

> Learn how to manage status page subscribers, including email confirmation, component-level subscriptions, and bulk import/export

Flashduty Status Pages allow users to actively subscribe to service status updates. When a new event is published or an event status changes, you can choose to push notifications to subscribers.

***

## Subscription methods

Different status page types support different subscription methods:

| Status page type | Subscription method | Description                                                                                |
| ---------------- | ------------------- | ------------------------------------------------------------------------------------------ |
| **Public**       | Email               | Visitors subscribe with an email address; email confirmation is required                   |
| **Public**       | RSS/Atom            | Subscribe to event updates via any RSS reader or automation tool; no confirmation required |
| **Internal**     | IM integration      | Internal users receive push notifications through linked IM platforms                      |

***

## User self-service subscription

### Email subscription (public status pages)

When a visitor enters an email address on a public status page, the system sends a confirmation email. The confirmation email is valid for **5 minutes**; after expiration, the visitor must resubmit.

<Steps>
  <Step title="Enter email address">
    The visitor enters their email address in the subscription area at the bottom of the status page.
  </Step>

  <Step title="Choose subscription scope">
    Select whether to subscribe to all updates, or only updates for specific components or events.
  </Step>

  <Step title="Confirm subscription">
    The visitor clicks the confirmation link in the received email to complete the subscription.
  </Step>
</Steps>

<Note>
  If the visitor changes their subscription scope before confirming, the system updates the pending subscription content without sending a new confirmation email.
</Note>

### IM subscription (internal status pages)

Internal organization users can receive event push notifications through their linked IM integrations (Feishu/Lark, Dingtalk, WeCom, Slack) after accessing the internal status page. IM subscriptions do not require email confirmation.

### RSS/Atom subscription (public status pages)

Every public status page automatically exposes an event feed in both RSS and Atom formats, so visitors can subscribe to updates through any RSS reader (Feedly, Inoreader, etc.) or automation tool. Feeds are anonymous — no account or email confirmation is required.

Each public status page serves the following four URLs. They return identical content; the `history.*` pair exists as an alias so that Atlassian Statuspage subscribers can migrate without changing their feed URLs:

| URL pattern               | Format           |
| ------------------------- | ---------------- |
| `{page-url}/feed.rss`     | RSS 2.0          |
| `{page-url}/feed.atom`    | Atom 1.0         |
| `{page-url}/history.rss`  | RSS 2.0 (alias)  |
| `{page-url}/history.atom` | Atom 1.0 (alias) |

`{page-url}` is the public URL of the status page — either the custom domain (for example `https://status.example.com`) or the default Flashduty-assigned URL.

Feed contents follow these rules:

* Includes events published within the last **90 days** (both incidents and maintenance), up to **50 items**, ordered by start time descending
* Only visible component impacts appear in the feed: components or sections marked as hidden are filtered out
* Each item's `<updated>` timestamp reflects the most recent timeline update, so readers can detect new activity on refresh
* Responses support `ETag` / `If-None-Match` and return `304 Not Modified` when nothing has changed

<Note>
  Feeds are available for **public** status pages only. Requesting a feed URL for an internal or non-existent page returns `404 Not Found`. For internal pages, use IM integrations instead.
</Note>

<Tip>
  If you are migrating from Atlassian Statuspage, you can swap the existing `history.rss` / `history.atom` subscription URLs for your Flashduty status page URL — no change is needed on the subscriber side.
</Tip>

***

## Subscription scope

Subscribers can flexibly choose their subscription scope:

| Scope            | Description                                                          |
| ---------------- | -------------------------------------------------------------------- |
| **All updates**  | Receive notifications for all events on the status page              |
| **By component** | Receive notifications only for events related to specific components |
| **By event**     | Receive only subsequent update notifications for specific events     |

When "All updates" is selected, component-level and event-level subscription settings are ignored — the subscriber receives all notifications.

***

## Administrator subscription management

### View subscribers

In the status page settings under **Subscription Management**, administrators can view the current subscriber list and filter by subscription method or component. The list supports pagination and displays each subscriber's email address (or user ID), subscription method, and subscribed components.

### Bulk import

Administrators can bulk import subscribers, useful for migration scenarios or pre-configuring subscriptions for specific user groups. The following fields are required for import:

| Field                  | Description                                        |
| ---------------------- | -------------------------------------------------- |
| **Recipient**          | Email address or user identifier                   |
| **Subscription scope** | All updates, or specific component IDs / event IDs |
| **Locale**             | Language preference for notifications              |

<Note>
  Subscriptions imported by administrators do not require email confirmation and take effect immediately. Importing a subscription for the same recipient replaces that recipient's previous subscription settings.
</Note>

### Export subscribers

Administrators can export the subscriber list, including each subscriber's recipient address, subscription method, and subscribed components.

***

## Subscriber self-management

Each subscriber has a unique **manage token** that allows them to self-manage their subscription:

* **View current subscription**: See which components and events they are subscribed to
* **Modify subscription scope**: Change subscribed components or events
* **Unsubscribe**: Completely opt out of the subscription

The manage token is included at the bottom of every notification email. Subscribers can click the "Manage subscription" link to access the self-management page.

### One-click unsubscribe from the mail client

Event change-notification emails also carry the RFC 8058 `List-Unsubscribe` and `List-Unsubscribe-Post` headers. Mainstream webmail clients — Gmail, Apple Mail, Outlook, Yahoo — render a native "Unsubscribe" button at the top of the message. When a subscriber clicks it, the mail client issues a one-shot POST to Flashduty and the subscription is removed immediately.

<Warning>
  One-click unsubscribe is **immediate and irreversible**: the request takes effect on arrival, no management page is involved, and no confirmation step is sent. To re-subscribe, the user must resubmit their email address on the status page and complete the confirmation flow again.
</Warning>

***

## Subscriptions and component lifecycle

When you delete a component, the system automatically removes all subscription records related to that component. Subscribers who were subscribed to that component will no longer receive related notifications.

Similarly, when you delete an event, the system automatically removes all subscription records related to that event.