How Slack Rebuilt Notifications 📣

Summary

Slack redesigned its legacy notification architecture to address user confusion, conflicting desktop and mobile preference systems, and tight coupling between notification content and push delivery. The engineering team unified four separate preference models into a single framework with three channel options: All new posts, Mentions, and Mute. To ensure safe rollback and backwards compatibility without direct database mutations, Slack implemented a read-time translation strategy alongside a new desktop_push_enabled preference and auto-saving cross-platform React UI components. This decoupling of activity from push delivery resulted in a fivefold sustained increase in settings engagement, reduced reliance on per-channel overrides, and eliminated synchronization mismatches across mobile and desktop clients.

Context

Slack's legacy notification system suffered from four conflicting mental models across desktop and mobile, inconsistent state synchronization between clients, and hidden coupling between what users were notified about and how notifications were delivered. Consequently, notification issues became one of the top three drivers of Customer Experience support tickets as users struggled to predict or control notification behavior.

Approach / What changed

Slack unified notification options into three settings (All new posts, Mentions, or Mute) and decoupled in-app activity from push notifications. To migrate users safely without risky database-level changes, Slack introduced a new desktop_push_enabled preference and used a read-time translation strategy to map legacy Off settings to Mentions with push disabled. The team also implemented auto-saving React preference modals and rewrote legacy iOS screens to establish cross-platform parity.

Takeaways

• Slack decoupled notification content triggers from push delivery channels, allowing users to track in-app activity while selectively disabling push notifications on desktop or mobile.
• To maintain backward compatibility and enable safe rollbacks during migration, engineers avoided direct database mutations and instead used read-time logic alongside a backfilled desktop_push_enabled field.
• Post-launch metrics showed a sustained 5x increase in settings engagement and a reduction in per-channel overrides, with the majority of users adopting the default Mentions and DMs configuration.

Related reading

• Grab · Sep 16, 2025

  Taming the monorepo beast: Our journey to a leaner, faster GitLab repo

  Grab's decade-old Go monorepo grew to 12.7 million commits and 250GB of Git data, causing Gitaly replication delays of up to four minutes that routed all read traffic exclusively to the primary node and slowed developer operations. After staging tests proved that shallow history reduced replication lag from hundreds of seconds to under three seconds, standard rewriting tools like git filter-repo and git rebase failed due to complex merge histories and repository scale. To overcome runner memory limits and lengthy git garbage collection cycles, the engineering team implemented a custom two-phase migration script. The script selectively migrated 2,000+ critical dependency tags and one month of recent history, flattening merge commits, embedding legacy hashes for traceability, and reducing total commit volume by 99.9%.

  Nagendra Gangwar

• Slack · May 5, 2026

  From SSH to REST: A Security-Driven Modernization of Slack’s EMR Data Pipelines

  Slack's data platform accumulated over 700 SSH-based Airflow operators executing jobs directly on AWS Elastic MapReduce clusters, creating broad security surfaces and operational instability. Stateful SSH connections frequently failed when Kubernetes pods restarted, leaving orphaned zombie processes and preventing infrastructure modernization such as migrating EMR clusters to child accounts. To eliminate SSH access, Slack adopted a REST-based architecture using Quarry, a gateway providing unified REST APIs and token authentication across compute engines. For non-Hadoop CLI workloads, Slack leveraged YARN Distributed Shell to execute arbitrary shell scripts stored in Amazon S3 within managed, isolated YARN containers. The phased migration achieved zero downtime across eight data regions, unlocking reliable monitoring, simplified onboarding, and future initiatives like Spark on Kubernetes.

  Mahendran Vasagam

• Slack · May 28, 2026

  Slack AI: The Path to Multi-Cloud

  Slack evolved its Slack AI serving infrastructure across multiple phases to handle enterprise LLM workloads reliably and securely. The initial deployment on AWS SageMaker provided zero-knowledge escrow VPC isolation and FedRAMP compliance, but engineers faced scaling latency, GPU scarcity, and significant operational overhead. Slack then migrated live traffic to Amazon Bedrock to leverage managed Model Units and eliminate model release lag without customer-facing incidents. However, fixed Provisioned Throughput commitments and regional peak traffic variations created persistent underutilization challenges. Consequently, Slack expanded into a multi-cloud orchestration architecture that normalizes disparate provider APIs, integrates unified cross-cloud telemetry, and routes traffic dynamically around latency spikes and outages.

  Shaurya Kethireddy

• Slack · Dec 1, 2025

  Streamlining Security Investigations with Agents

  Slack's Security Engineering team handles billions of daily security events and needed a reliable way to streamline on-call alert triage. An initial prototype relying on a single 300-word prompt produced inconsistent results and frequently reached spurious conclusions without properly challenging assumptions. To gain precise control, the team decomposed the workflow into chained model invocations with structured JSON outputs organized across three agent personas: a Director, four domain experts, and a Critic. Domain experts gather raw evidence through tool calls, the Critic evaluates finding quality and synthesizes a timeline, and the Director steers investigation phases using tiered model costs. The multi-agent system enables engineers to supervise investigations via a real-time dashboard while uncovering emergent issues like credential exposures across process ancestry chains.

  Dominic Marks