Subscription methods
Different status page types support different subscription methods:| Status page type | Subscription method | Description |
|---|---|---|
| Public | Visitors subscribe with an email address; email confirmation is 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.Enter email address
The visitor enters their email address in the subscription area at the bottom of the status page.
Choose subscription scope
Select whether to subscribe to all updates, or only updates for specific components or events.
If the visitor changes their subscription scope before confirming, the system updates the pending subscription content without sending a new confirmation email.
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.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 |
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 |
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 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