Subscription methods
Different status page types support different subscription methods: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.1
Enter email address
The visitor enters their email address in the subscription area at the bottom of the status page.
2
Choose subscription scope
Select whether to subscribe to all updates, or only updates for specific components or events.
3
Confirm subscription
The visitor clicks the confirmation link in the received email to complete the subscription.
When a pending subscription already exists for the same email address, submitting the form again neither changes the scope awaiting confirmation nor sends another confirmation email — the scope chosen on the first submission is what takes effect. To change it, resubmit after the confirmation email expires (5 minutes). A confirmed subscriber who changes scope must resubmit the form and click the link in the new confirmation email: their existing subscription stays as it is until they confirm, and the new scope replaces it once confirmed. Alternatively, they can use the manage token in any notification email to update it directly.
Slack subscription (public status pages)
When Slack subscriptions are enabled on a public status page, visitors can route incident and maintenance updates directly into a Slack channel:1
Choose subscription scope
Open the subscription dialog on the status page, switch to the Slack tab, and choose all updates or specific components.
2
Authorize in Slack
Click Add to Slack, pick the target workspace and channel on the Slack authorization page, and approve the request.
3
Receive updates
The subscription takes effect immediately. Every Slack notification card includes links to manage subscription scope or unsubscribe.
Microsoft Teams subscription (public status pages)
When Microsoft Teams subscriptions are enabled on a public status page, visitors can receive Adaptive Card updates in a Teams channel via Microsoft Teams Workflows:1
Create a Workflows webhook URL in Teams
In Microsoft Teams, open the target channel’s More options (
...) → Workflows → “Send webhook alerts to a channel” (or “Post to a channel when a webhook request is received”) and copy the generated webhook URL (*.logic.azure.com or *.environment.api.powerplatform.com).2
Submit on the status page
Open the subscription dialog on the status page, switch to the Teams tab, paste the Workflows webhook URL, choose all updates or specific components, and submit.
Legacy Office 365 Connector webhook URLs (
*.webhook.office.com) have been retired by Microsoft and are rejected. Use a Teams Workflows webhook URL instead.IM subscription (internal status pages)
Internal organization users can receive event push notifications on 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 has an event feed in RSS and Atom formats. Visitors can subscribe with any RSS reader (Feedly, Inoreader, and so on) or automation tool. Feeds are anonymous and need no account or email confirmation. Each public status page serves the following four URLs. They return identical content; thehistory.* pair exists as an alias so that Atlassian Statuspage subscribers can migrate without changing their feed URLs:
{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: the feed leaves out hidden components and sections
- Each item’s
<updated>timestamp reflects the most recent timeline update, so readers can detect new activity on refresh - Responses support
ETag/If-None-Matchand return304 Not Modifiedwhen nothing has changed
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.Subscription scope
Subscribers can flexibly choose their subscription scope:
When “All updates” is selected, Flashduty ignores component-level and event-level subscription settings — the subscriber receives all notifications.
Administrator subscription management
Subscription settings
On the Subscriptions page of the status page settings, administrators control subscription availability per channel:- Public status pages: independent switches for Email notifications, Slack notifications, and Microsoft Teams notifications. Turning off a channel hides that tab from visitors and stops sending notifications through it, even if “Notify subscribers” is checked when publishing an event.
- Internal status pages: a page-level switch for IM notifications.
- Email (public status pages): event notification emails count toward the Flashduty account’s email quota. For Free plan accounts, Flashduty stops sending event notification emails once the quota is exceeded. For paid plan accounts, emails beyond the quota are billed separately, and notifications stop only when the account is in arrears.
- Slack & Microsoft Teams (public status pages): notifications are delivered directly to subscribed channels and do not consume your Flashduty email quota.
- IM (internal status pages): event notifications count toward the API call quota of the corresponding IM platform; when the IM platform’s API quota is exceeded, Flashduty stops sending notifications. API call limits usually depend on the IM platform pricing plan your organization uses.
View subscribers
In the Subscriber List section of the Subscriptions page in the status page settings, administrators can view the current subscriber list and filter by component and subscription method (Email, Slack, Microsoft Teams, or IM). The list supports pagination and displays each subscriber’s subscription method, recipient label (such as email address,#channel (Workspace) for Slack, or Teams Webhook (<id>) for Teams), subscribed components, and language preference.
Bulk import
Administrators can bulk import subscribers, useful for migration scenarios or pre-configuring subscriptions for specific user groups. The console has no import entry; import through the API (see the bulk import subscribers API). The following fields are required for import: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.
Export subscribers
Administrators can click Export CSV in the Subscribers list to 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