Automated Dedicated Incident Channels is a new default behavior where PagerDuty automatically creates a focused Slack channel for each major incident (P1/P2 by default). This centralizes communication, reduces noise, and provides a complete audit trail for post-incident reviews. It's considered an industry best practice.

Your existing workflows will NOT be affected. The new global feature respects workflow-level settings. If you already have dedicated channels created via Incident Workflows, those configurations (including custom topics and triggered actions) will continue to work exactly as before. The hierarchy is: workflow-level settings take precedence over global defaults.

Channels in Slack automatically become archived every 30 days. You can setup auto archiving with different behavior via Incident Workflows.

YES. Your admin can turn off the global setting in their Slack configuration. They can also customize when channels are created (e.g., by priority/severity) and how they're named. These are found in the Slack integrations area (navigate to the Integrations section). Click on “View” when you see your workspace listed.

• Triage Channel (formerly "Responder Notification Channel"): Where alerts land for initial triage; always threaded
• Dedicated Incident Channel: A focused space created for each major incident where responders collaborate
• Announcement Channel (formerly "Stakeholder Notification Channel"): Where high-level updates are broadcast to stakeholders; always threaded

YES. Customers can keep the ability to triage incidents in a single channel and only move certain incidents to dedicated channels. They can switch the global config to OFF but still use Incident Workflows or the manual button to create dedicated incident channels when needed..