Merge pull request #26 from flashcatcloud/doc-review/2026-03-23-120000

docs: doc-review findings for week of 2026-03-23

Author: ysyneu

en/on-call/channel/create-edit.mdx

@@ -40,23 +40,30 @@ Proper planning can significantly improve operational efficiency.
   <Step title="Fill in Basic Information">
     Enter **Channel Name**, preferably named after business type or team
   </Step>
-  <Step title="Select Management Team">
-    Select **Management Team**, members of this team have full operational permissions for the channel
+  <Step title="Select Owning Team">
+    Select **Owning Team**, members of this team have full operational permissions for the channel
+  </Step>
+  <Step title="Set Managing Team (Optional)">
+    If you need to delegate channel management permissions to other teams, set **Managing Teams** (up to 3). When set, managing teams take over management permissions (edit, delete, etc.) from the owning team, but both teams retain read access. This feature must be enabled by contacting the Flashduty team; it is not enabled by default.
   </Step>
   <Step title="Set Access Level">
     - **Public**: Visible to all users in the account, can view and operate incidents but cannot modify channel configuration
-    - **Private**: Only visible to management team, creator, and account administrators
+    - **Private**: Only visible to the owning team (or managing team), creator, and account administrators
   </Step>
-  <Step title="Configure Auto-close Timeout (Optional)">
-    - **Auto-close after incident trigger**: Timer starts from when the incident is first triggered, suitable for alerts without automatic recovery
-    - **Auto-close after alerts stop merging**: Timer starts from the last alert merge, suitable for scenarios with alert grouping enabled
+  <Step title="Configure Auto-resolve Timeout (Optional)">
+    Enable the auto-resolve timeout toggle, then configure the following parameters:
+    - **Window timing start**: Select **Incident trigger** (timer starts from when the incident is first triggered, suitable for alerts without automatic recovery) or **Alerts stop merging** (timer starts from the last alert merge, suitable for scenarios with alert grouping enabled)
+    - **Timeout duration**: Set the timeout duration in minutes, hours, or days, up to a maximum of 30 days
   </Step>
   <Step title="Configure Close with Alerts (Optional)">
     Enabled by default. When enabled, incidents automatically close when all associated alerts recover. When disabled, alert recovery does not auto-close the incident — you need to close it manually or rely on the auto-close timeout policy.
   </Step>
   <Step title="Enable Outlier Incident Detection (Optional)">
     When enabled, incident lists and notification content will include an "Outlier Incident" indicator for quick identification. [Learn more](/en/on-call/incident/outlier-incidents)
   </Step>
+  <Step title="Enable External Reporting (Optional)">
+    When enabled, external personnel can submit incident tickets via a shareable external reporting link without logging in. The system generates a shareable link that you can distribute to external personnel. Disabling external reporting immediately invalidates all previously shared links; re-enabling generates a new link.
+  </Step>
   <Step title="Complete Creation">
     Click **Next** to complete creation
   </Step>
@@ -126,12 +133,19 @@ Links support two open modes: **Open in New Tab** and **Open in Embedded iframe*
 
 ### Changing Configuration
 
-Go to Channel Details → **Basic Settings** to modify:
+Go to Channel Details and modify configuration across two settings tabs:
 
+**Basic Settings**:
 - Channel name, description
-- Management team
-- Auto-close timeout policy
+- Owning team
+- Managing team (must be enabled by contacting the Flashduty team; up to 3 managing teams; when set, managing teams take over management permissions from the owning team)
+- Access level (public or private)
+
+**Advanced Settings**:
 - Close with alerts toggle
+- Auto-resolve timeout (toggle, window timing start, timeout duration)
+- Outlier incident detection
+- External reporting (when enabled, generates a shareable link for external personnel to submit incident tickets without logging in)
 
 ### Disabling and Deleting
 
@@ -153,14 +167,17 @@ See [Search and View Incidents](/en/on-call/incident/search-view-incident) for d
 ## FAQ
 
 <AccordionGroup>
-  <Accordion title="What's the difference between management team and access level?" icon="circle-question">
-    - **Management Team**: Controls who can modify channel configuration (integrations, escalation rules, noise reduction rules, etc.)
-    - **Access Level**: Controls who can see the channel and its incidents. Public channels are visible to everyone but only the management team can modify configuration; private channels are only visible to the management team
+  <Accordion title="What's the difference between owning team, managing team, and access level?" icon="circle-question">
+    - **Owning Team**: The team that owns the channel and has full management permissions (edit, delete, etc.) by default
+    - **Managing Team**: When set, managing teams take over management permissions (edit, delete, etc.) from the owning team, but both teams retain read access. This feature must be enabled by contacting the Flashduty team
+    - **Access Level**: Controls who can see the channel and its incidents. Public channels are visible to everyone but only the owning team (or managing team) can modify configuration; private channels are only visible to the owning team (or managing team)
   </Accordion>
 
-  <Accordion title="How to choose between the two auto-close timeout policies?" icon="circle-question">
-    - If the alert source doesn't have automatic recovery events and alert grouping is not enabled, choose **Auto-close after incident trigger**
-    - If alert grouping is enabled, choose **Auto-close after alerts stop merging** to ensure all alerts within the grouping window are processed
+  <Accordion title="How to configure auto-resolve timeout?" icon="circle-question">
+    Enable the auto-resolve timeout toggle in Advanced Settings, then select a window timing start and timeout duration:
+    - **Window timing start** set to **Incident trigger**: Timer starts from when the incident is first triggered, suitable for alert sources without automatic recovery events and when alert grouping is not enabled
+    - **Window timing start** set to **Alerts stop merging**: Timer starts from the last alert merge, suitable for scenarios with alert grouping enabled, ensuring all alerts within the grouping window are processed
+    - **Timeout duration** supports minutes, hours, or days as units, up to a maximum of 30 days
   </Accordion>
 
   <Accordion title="Is incident data still available after deleting a channel?" icon="circle-question">

en/on-call/channel/escalation-rule.mdx

@@ -87,6 +87,8 @@ In each escalation level, you can enable the **Loop Notification** feature. When
 - **Timeout without acknowledgment**: No one acknowledges within N minutes after incident trigger
 - **Timeout without closure**: Incident not resolved within N minutes after trigger
 
+The minimum escalation timeout is 1 minute.
+
 **Typical Scenarios**:
 
 | Scenario | Escalation Path |

en/on-call/channel/noise-reduction.mdx

@@ -99,8 +99,9 @@ Flashduty On-call provides two grouping modes:
 
 | Configuration | Description |
 | :------- | :----------------------------------- |
-| **Grouping Window** | Only group alerts within the time window, alerts outside the window trigger new incidents |
-| **Window Type** | **Tumbling** (default): Fixed timer starts from incident creation, stops grouping when the window duration is reached. **Sliding**: Timer resets each time a new alert merges in, the window recalculates from the last merge |
+| **Aggregation Window** | Optional toggle. When disabled, new alerts continue merging into the incident until the incident is closed. When enabled, alerts within the window are merged; alerts arriving after the window expires are grouped into a new incident |
+| **Window Timing Start** | Only configurable when the aggregation window is enabled. **Incident trigger** (default): Fixed timer starts from incident creation, stops grouping when the window duration is reached. **Alert merges into incident**: Timer resets each time a new alert merges in, the window recalculates from the last merge |
+| **Window Duration** | Only configurable when the aggregation window is enabled. Set the duration of the aggregation window |
 | **Alert Storm Warning** | When merged alert count reaches the configured threshold, the system records an alert storm event in the incident timeline and triggers a warning notification, prompting urgent handling |
 | **Strict Grouping** | When enabled, empty label values are treated as different; when disabled, empty values are treated as the same (not supported for intelligent grouping) |
 
@@ -329,6 +330,7 @@ When a new alert meets conditions, and there's an **active incident** (not close
   <Accordion title="What's the maximum number of events a single alert can be associated with?" icon="circle-question">
     - **Rule-based Grouping**: No limit, default maximum grouping window is 24 hours. After 24 hours from alert trigger, new events create new incidents
     - **Intelligent Grouping**: No limit, default maximum grouping window is 24 hours, with certain subscription plans supporting extension up to 30 days. After exceeding the window, new events create new incidents
+    - If the aggregation window is disabled, alerts continue merging into the existing incident until the incident is closed, with no time limit
   </Accordion>
 </AccordionGroup>
 

en/on-call/incident/alert-management.mdx

@@ -15,9 +15,8 @@ The alert list displays the following information:
 | :--- | :--- |
 | **Severity** | Displays alert severity as a color bar (Critical, Warning, Info) |
 | **Title** | Alert title description |
-| **Processing Status** | Whether the alert is closed (Closed / Not Closed) |
-| **Recovery Status** | Whether a closed alert has auto-recovered (Recovered / Not Recovered) |
-| **Duration** | Time elapsed from alert trigger to current time or closure |
+| **Processing Status** | Current recovery status of the alert (Recovered / Active). The list header supports quick filtering by "Active Alerts" and "Recovered Alerts" tabs |
+| **Incident Progress** | Current processing progress of the incident associated with this alert |
 | **Associated Events** | Number of raw events associated with the alert |
 | **Associated Incident** | The incident this alert belongs to; click to navigate to incident details |
 | **Trigger Time** | When the alert was first triggered |

en/on-call/incident/search-view-incident.mdx

@@ -89,7 +89,7 @@ Incident details is the main entry point for investigating incidents, displaying
 | 5 | Comprehensive Info | Shows incident attributes, processing status, [images](https://developer.flashcat.cloud/api-344943718), and responder info |
 | 6 | Custom Fields | Custom field configuration area |
 
-You can switch tabs above to view more detailed **Associated Alerts**, **Timeline**, and **Change History** for root cause analysis. For closed incidents, the system also shows a **Resolution** page displaying root cause and resolution.
+You can switch tabs above to view more detailed **Associated Alerts**, **Timeline**, **Change History**, and **Post-Mortem**. Post-mortem supports creating and editing post-mortem reports directly from the incident details. See [Post-Mortem](/en/on-call/post-mortem/create-edit-post-mortem) for details. For incidents with existing resolution records, the system still displays the **Resolution** tab.
 
 ### Change History
 

en/on-call/incident/what-is-incident.mdx

@@ -69,6 +69,7 @@ Incidents can be triggered in the following ways:
 
 - **Auto-trigger**: Flashduty On-call receives an alert event from an integration (like Zabbix notification), event auto-triggers an alert, alert auto-triggers an incident
 - **Manual trigger**: Click **Create Incident** button in Flashduty On-call console, fill in title, description, severity, etc. to trigger a new incident
+- **External reporting**: After enabling external reporting, external personnel can submit incident tickets through a dedicated link without logging into a Flashduty account. See [Channel Configuration](/en/on-call/channel/create-edit) for details
 </Step>
 
 <Step title="Assignment and Notification">

en/on-call/integration/alert-integration/routing-rules.mdx

@@ -50,6 +50,7 @@ When using name mapping mode, if corresponding channel doesn't exist, delivers t
 | Insert Rule | Quickly insert new rules before or after a specified rule without manually dragging to adjust position |
 | Filter Rules | Filter by channel to quickly locate all rules delivering to a specific channel, ideal for scenarios with many rules |
 | Edit History | View historical configuration versions, compare differences, and quickly restore (see details below) |
+| Route Preview | After editing routing rules, click the preview button and select up to 20 real alerts to see how the modified rules would route each alert. The system displays routing differences between old and new rules, including added, removed, and unchanged channels |
 
 ### Edit History
 

en/platform/configure-sso.mdx

@@ -75,7 +75,7 @@ LDAP single sign-on is only supported in the **private deployment version**.
 | LDAP URL | LDAP service address, e.g., `ldap://10.10.10.10:389` |
 | BIND DN | Username for connecting to LDAP, e.g., `cn=admin,dc=flashduty,dc=com` |
 | BIND DN Password | Password for connecting to LDAP, stored encrypted in the database |
-| Encryption | Supports **TLS** and **StartTLS** encryption methods (mutually exclusive, only one can be enabled). After enabling either method, you can optionally **skip SSL/TLS certificate verification**; if not skipped, you need to provide the SSL/TLS certificate path |
+| Encryption | Supports **TLS** and **StartTLS** encryption methods (mutually exclusive, only one can be enabled). After enabling either method, you can optionally **skip SSL/TLS certificate verification**; if not skipped, you can optionally provide the SSL/TLS certificate path |
 | User DN | Defines where to start searching for users, e.g., `ou=people,dc=flashduty,dc=com` |
 | Auth Filter | Custom filter expression for retrieving user DN information, basic form: `(&(mail=%s))`. Note: Opening and closing parentheses are required |
 | Field Mapping | Flashduty extracts user email, username, phone, and Group information from the identity provider through mapped fields. Email is a required mapping field. The Group field defaults to `memberOf` and is used for role and team synchronization |

en/platform/team-members.mdx

@@ -49,6 +49,8 @@ A team is a collection of members. You can group members with different responsi
 
 ---
 
+In the member list, a warning icon appears next to unverified email addresses or phone numbers. Unverified contact methods cannot receive alert notifications. Please remind members to complete verification promptly.
+
 ### Invitation Methods
 
 <Tabs>