Channel Name: Recommended to name and plan based on department, team, or business type for better understanding of the channel's purpose.
Description: Briefly summarize the business handled by this channel and the types of alerts it receives.
Management Team: Set the management team during creation. Team members have full operational permissions for the channel, while non-creators have read-only access to channel configurations.
Auto-close Timeout: Incidents not closed within N minutes will be automatically closed by the system (applies to all new incidents in this channel). Timeout-closed incidents will also receive corresponding closure notifications (notification channels depend on escalation rule configuration). Access Level: The channel is visible to which users, public means all users can view and operate incidents within the channel, private means only the creator, management team, and main account can view and operate incidents within the channel.
If incident assignment planning isn't ready, you can skip setting escalation rules and configure them after creation.
Integration types added during creation are exclusive integrations that only apply to this channel and can be configured later after creation.
Account members can see all channels but can only operate those they're responsible for.
Hover over a channel and click the star to favorite or unfavorite it.
By default, all channels are shown; you can view channels related to "me" through "My Managed" or "My Favorites".
When you have many channels but your focused channels are sorted lower, you can use the sorting feature in the top right to move your focused channels forward.
Sorting is customizable and only affects the current user, not others.
Channel name, description, auto-close timeout, and management team can be modified in Channel Details -> Basic Settings.
Disabled channels stop receiving alerts but allow continued operation of incidents and related configurations.
Deleting a channel doesn't delete existing incident data, but deleted channels cannot be recovered, so proceed with caution.
Shows all incidents in the channel, defaulting to open incidents; filter by progress status.
Filter by incident status, responders, time, title, and other conditions.
Select multiple incidents with the same status for batch closing, acknowledging, etc.
Merge combines multiple incidents into one for processing, supporting cross-channel incident merging.
Integrations created under a channel are exclusive integrations, applying only to that channel.
Each integration type generates its webhook URL upon creation; different integration types are incompatible.
Drop rules discard events meeting specified conditions, configurable by integration type, severity, etc.
With multiple drop rules, priority matches from high to low, stopping at first match.
Dropped events are completely invisible in the system. If alerts are missing, check drop rule configurations.
Manage incident notification rules, channels, escalation rules, etc.
Incident notifications match strategies in sequence, stopping after first match.
Multiple strategies can be freely reordered; ensure notification rules meet business requirements before adjusting.
