Fix Slack Notifications Not Working

When Slack notifications stop working, there are four separate systems involved — Slack’s own settings, Windows notification permissions, the Windows notification service, and Focus Assist. Most fix guides only check one or two of them. That’s why people end up reinstalling Slack and still get nothing. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.

The fastest diagnostic: open Settings → System → Notifications and confirm Slack is set to “On” with banner and sound both enabled. If it’s already on there, the problem is at the Slack app level — not Windows — and you can skip straight to the Slack notification settings section below.

Start with whichever layer your symptoms point to. If you get notifications on your phone but not on desktop, it’s a Windows-side problem. If you get nothing anywhere, it’s a Slack-side notification settings issue. Working through the wrong layer first is the most common reason this drags on for hours.

The Four Layers — Checked in Order

Layer 1: Windows Notification Settings

Settings → System → Notifications:

• “Notifications” master toggle at the top → must be On
• Scroll to the app list → Slack → must be On
• Click Slack → expand its notification settings → confirm “Show notification banners” and “Show in notification centre” are enabled

The per-app settings when you click on Slack in the list control both banner notifications (the popup) and the notification centre count. Enabling the master toggle but leaving per-app banners disabled produces a situation where you get a count in the notification centre but no visible popups — which many users experience as “notifications not working.”

Layer 2: Slack Notification Settings

Slack has its own notification configuration that works independently from Windows. Slack → click your name or workspace name (bottom left of the sidebar) → Preferences → Notifications. Check:

• “Notify me about” → set to “Direct messages, mentions and keywords” at minimum, or “All new messages” for noisier notifications
• “Use different settings for my mobile devices when I’m active there” → if mobile notifications are selected when the desktop should be active, desktop notifications may be suppressed
• Sound notifications → enable if you also need audio alerts

Also check the bell icon at the bottom of the Slack sidebar — if it shows a number or moon icon, notifications are paused. Click it to see the pause status and unpause if needed.

Layer 3: Focus Assist / Do Not Disturb

Windows Focus Assist and Do Not Disturb suppress notifications from all apps while active. These can be activated automatically — during presentations (when mirroring to a display), during certain hours, or when Windows detects game mode.

Settings → System → Focus → check whether “Focus” or “Do Not Disturb” is active. Also check: Settings → System → Notifications → scroll to the bottom → “Automatic rules” — these can activate Do Not Disturb on schedules or triggers you may have forgotten about. Turn off any automatic rules that are suppressing notifications during your working hours.

Layer 4: Slack’s Pause Notification Feature

Slack has its own “Pause notifications” feature that works independently from Windows. It can be set to pause for 30 minutes, several hours, or until a specific time — and it persists across Slack restarts. After the pause period ends, notifications resume automatically, but it’s easy to forget a pause was set.

Check: click the bell icon in the Slack sidebar (usually bottom left, next to your name) → if it shows “Notifications paused until [time]” or shows a duration, click “Turn off snooze” or the bell again to resume notifications immediately.

Fix: Restart Slack Properly

Slack’s notification system can get into a stuck state where notifications are correctly configured but not being delivered — usually after a crash, an update, or when Slack has been running for many days without a restart. A complete restart (not just closing the window) clears this:

System tray → right-click the Slack icon → Quit Slack. Confirm all Slack processes are gone in Task Manager. Wait 15 seconds. Reopen Slack. After restarting, test by having someone send a message to confirm notifications deliver.

Browser Version vs Desktop App

Slack’s browser version (slack.com in Chrome or Firefox) uses the browser’s notification permissions, which are separate from the Windows notification system. If you use Slack in a browser and notifications stopped: click the padlock icon in the browser address bar → Site settings → Notifications → Allow for slack.com. Also check the browser notification settings globally: in Chrome, chrome://settings/content/notifications → confirm Slack isn’t in the “Not allowed” list.

Slack on Multiple Workspaces

Each Slack workspace has its own notification settings. A notification from Workspace A arrives correctly while Workspace B shows nothing — because Workspace B’s notification settings are set to “Nothing” while A is set to “All messages.” Check each workspace separately: Slack notification settings → select the workspace from the dropdown at the top of the Preferences page → configure notifications for that specific workspace.

Mention and Keyword Notifications

Slack’s “Direct messages, mentions and keywords” setting sends notifications only when someone @-mentions you directly or uses a keyword you’ve set. Messages sent to channels without mentioning you produce no notification in this mode. If you need notifications for all activity in specific channels: right-click the channel in the sidebar → Change notifications → “All new messages” for that specific channel — overriding the global setting for high-priority channels.

Our guide on Slack not working covers the broader Slack connectivity and performance issues — the cache clear and reinstall approach applies when notifications are broken alongside other Slack functionality. For Windows notification issues affecting multiple apps simultaneously, our Windows taskbar and notification area guide covers the shell component reset that restores the notification infrastructure. Slack’s notification troubleshooting documentation covers the Do Not Disturb schedule, the status-based notification suppression (active on mobile suppresses desktop), and the per-workspace and per-channel notification override settings.

Slack Notification Sounds Specifically

Notification banners appearing but no sounds: Slack plays notification sounds through the system default audio device. When the audio output changes (headphones connected or disconnected, Bluetooth speaker connected) and Windows switches the default device, Slack’s notification sounds may be going to the old device or a device that’s no longer active.

In Slack Preferences → Notifications → check “Sounds” — confirm the notification sound is selected (not “None”). Also confirm Windows is routing audio to the correct device. The notification sound setting in Slack uses the Windows default audio output — right-click speaker icon → check which device is currently default. If the default device has no audio path (disconnected headphones, inactive HDMI monitor), Slack’s sounds play silently to a device that can’t output them.

Slack Running in Quiet Hours on Corporate Devices

Microsoft Intune and device management systems can enforce notification quiet hours policies on managed Windows devices. When these policies are active, they override both Windows notification settings and Slack’s own notification configuration — notifications are suppressed at the OS level regardless of how Slack or Windows notifications are configured by the user.

The indicator: notifications work on a personal device or outside work hours on the corporate device, but consistently don’t appear during business hours on the managed machine. This is an IT policy matter rather than a user-configurable issue. If this is affecting your work, report to IT that Slack notifications are being suppressed during work hours — the policy may be misconfigured, or an exception may be grantable for specific applications.

Windows Notification Backlog and Clearing

The Windows notification centre can accumulate hundreds of notifications and sometimes gets into a state where new notifications fail to appear even when settings are correct — because the notification service is overwhelmed or the display queue is backed up. Clearing the notification backlog sometimes restores the notification pipeline:

Click the notification/date area in the taskbar (bottom right) → scroll through all notifications → click “Clear all notifications” at the top. After clearing the backlog, the notification service refreshes its state and subsequently delivers new notifications correctly. This is more of a workaround than a fix, but it’s immediate and costs nothing to try before more involved troubleshooting.

Slack’s Windows Store Version vs Desktop Download

Slack is available from both the Microsoft Store and as a direct download from slack.com. These versions behave differently in how they interact with Windows notifications. The Store version uses Windows App notification infrastructure which sometimes conflicts with Windows Update changes to the notification system. The direct download version uses standard Win32 notification APIs that tend to be more stable across Windows updates.

Check which version is installed: Settings → Apps → Installed apps → search “Slack” → look at the publisher. “Slack Technologies, LLC” typically indicates the Store version. If notifications stopped after a Windows update and Slack is the Store version, switching to the direct download version from slack.com/downloads sometimes resolves Windows Update-caused notification incompatibilities between Slack and the Windows notification infrastructure.

Notification Centre vs Toast Notifications

Windows has two notification delivery mechanisms: toast notifications (the popup that appears briefly) and notification centre entries (the count visible by clicking the notification area). These can behave differently — you might get notification centre count updates but no toast popups, or vice versa.

If toast popups stopped but the notification count still updates: Settings → System → Notifications → click Slack → confirm “Show notification banners” is On (this controls the popup specifically). If both stopped: the notification delivery chain has a broader issue — check the notification service is running: Win + R → services.msc → find “Windows Push Notifications System Service” → confirm Running and set to Automatic. This service handles toast notification delivery; if it’s stopped, no app receives toast notifications.

Reinstalling Slack for Persistent Notification Failures

When all configuration checks show correctly — Windows notifications enabled for Slack, Slack notifications configured correctly, no Focus/DND active, Slack bell not paused — but notifications still don’t arrive: the Slack installation’s notification registration with Windows may be corrupted.

A clean reinstall rebuilds this registration:

1. Quit Slack completely
2. Settings → Apps → Slack → Uninstall
3. Delete remaining folders: %appdata%Slack and %localappdata%Slack
4. Restart the PC
5. Install from slack.com/downloads (not the Microsoft Store if switching)
6. Sign in → test notifications with a colleague

The folder deletion step is necessary — without it, the reinstaller recovers the corrupted notification registration from the leftover data. After the clean reinstall, Slack registers fresh with Windows’ notification system and subsequent notifications deliver correctly.

Testing Notification Delivery

A reliable way to test whether notifications are working after applying fixes: have a colleague send you a direct message, then step away from the keyboard and leave Slack in the background. If the notification appears within 30 seconds of the message being sent, the notification pipeline is working. If it doesn’t: check whether the Slack window was in the foreground recently (Slack suppresses notifications when the app window has focus, because the message is already visible) — move to a different application window for 60 seconds before testing, so Slack registers as a background application for notification purposes.

A common but easy-to-miss scenario: notifications working on mobile but not desktop. Slack’s “use different settings for mobile devices when active” feature suppresses desktop notifications when Slack’s mobile app was recently active. If you checked your phone in the last 10 minutes, Slack considers you “active on mobile” and may suppress desktop notifications to avoid double-notifying. This isn’t a bug — it’s intentional. The behaviour can be disabled: Slack Preferences → Notifications → “Use different settings for my mobile devices when I’m active there” → toggle off. After disabling, Slack notifies all devices simultaneously regardless of recent mobile activity.

For users on Slack Enterprise Grid (multi-workspace enterprise deployments): notification settings can be configured at the workspace level by administrators, potentially overriding individual user preferences. If notification settings appear correct from the user’s perspective but notifications still don’t arrive for specific channels or workspaces, the Enterprise Grid admin may have restricted notification types or set mandatory quiet hours for the workspace. Checking with the Slack workspace administrator whether any notification policies are applied to the workspace is worth doing before continuing with local troubleshooting — admin-controlled policies can’t be overridden by users.

One scenario worth flagging specifically: if Slack notifications stopped working for an entire team simultaneously — not just one person — the cause is almost certainly server-side at Slack or a network-level block rather than individual machine configuration. Check status.slack.com for any notification-related incidents. Slack has had outages that specifically affected notification delivery while the rest of the service appeared functional. If status.slack.com shows any notification-related degraded service or ongoing incident, the fix is waiting for Slack’s resolution rather than spending time on local configuration that won’t address a server-side delivery problem.