Slack notifications going silent — no banner, no sound, no badge count — is one of those problems that happens gradually and you only notice when you miss something important. The fix is almost always in one of three places: Slack’s own notification preferences, Windows 11’s per-app notification settings, or Do Not Disturb being active on one or both sides. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The fastest diagnostic: send yourself a test direct message (open a DM with yourself, type something, send). Watch for the banner in the bottom-right of the screen. If it appears: Slack’s system is working and the problem is specific to channels or mentions. If no banner appears: one of the notification layers is blocked. This 30-second test tells you immediately whether you have a configuration problem or an app-level problem.
Slack’s notification preferences — the main control panel
Slack → top-left name/workspace menu → Preferences → Notifications. This is where most Slack notification problems originate.
Key settings to verify:
- Notify me about: set to “All new messages” for full notification on every message, or “Direct messages, mentions & keywords” if you only want important pings. “Nothing” here means complete silence regardless of other settings.
- Notification schedule: if a schedule is configured, Slack silences notifications outside working hours. It silences itself after 5pm and you forget it was on. Toggle this off to get 24/7 notifications, or extend the schedule window.
- Use different settings for my mobile devices when I’m not active on desktop: if checked, Slack uses different rules when you haven’t used the desktop for a while. These “away” rules might be more restrictive than you intended.
Do Not Disturb — Slack’s own and Windows’s
Two separate Do Not Disturb systems can mute Slack notifications:
Slack’s DND: Click the bell icon at the top of the Slack sidebar → if there’s a checkmark next to a duration, DND is on. Click “Turn off” to disable it. Slack’s DND automatically activates outside your notification schedule and can also be turned on manually. If the bell has a slash through it, DND is active for Slack.
Windows 11 Focus/DND: Look at the taskbar clock area — if there’s a moon icon, Windows Do Not Disturb is on and Slack banners are suppressed system-wide. Click the clock → toggle off. Settings → System → Focus → check if any automatic rules are triggering it unexpectedly (such as “During these hours” or “When duplicating my display”).
Both systems need to be off for notifications to appear. Either one being active silences everything.
Windows 11 notification settings for Slack
Windows controls per-app notification permissions independently. Settings → System → Notifications → scroll down to find “Slack” in the app list. Three things to check:
- The Slack toggle must be On. If it’s off: no Slack notifications reach Windows at all, regardless of Slack’s own settings.
- Click the “Slack” entry (not just the toggle) to expand options — “Show notification banners,” “Play a sound,” and “Show in notification center” are each individually configurable. If banners are off but Action Center is on: you’ll see them accumulate in Action Center but no popup appears. Enable “Show notification banners” to get the popup again.
- Notification priority: set to “High” if you want Slack notifications to appear even during Focus sessions with a priority list configured.
Channel-specific notification settings
Slack allows per-channel notification overrides. If only specific channels are silent while others work: the channel settings are the issue, not a system-wide problem.
Click the channel name → gear icon → “Notifications” → see what’s configured. Common causes:
- Channel is set to “Off” — no notifications from this channel regardless of Slack-wide settings
- Channel is set to “Only mentions” but the messages you’re missing aren’t @-mentioning you
- Someone muted the channel (bell with a slash next to the channel name) — muting overrides all notification settings for that channel
To unmute: right-click the channel in the sidebar → Unmute channel. Or click the channel name → Notifications → change to your preferred setting. Muted channels show a faded appearance in the sidebar on some Slack themes.
Our guide on Windows notification troubleshooting covers the system-level settings that affect Slack alongside every other app, and our Discord notification troubleshooting covers the parallel notification issues in Discord (very similar architecture). For Slack’s specific desktop app notification configuration, Slack’s help center covers the notification preferences and the macOS/Windows-specific workarounds in detail.
Notification sound specifically missing
If Slack banners appear but you don’t hear a sound: either the system volume is muted for Slack specifically, or Slack’s sound setting is off.
Slack sounds: Preferences → Notifications → “Sound & appearance” → “Play a sound when receiving a notification” — enable it. Then choose which sound (there are multiple). The default “Ding” is pleasant enough; some users prefer “Hummus” or custom sounds for their workspace.
Windows volume mixer: right-click the speaker icon → Open Volume Mixer → look for “Slack” or “Electron” (Slack is built on Electron) → confirm the volume isn’t at 0 and isn’t muted (no red X). Volume Mixer settings persist even after Slack restarts, so muting it once keeps it muted until you manually unmute.
Multiple workspaces — which one’s actually configured
If you’re in multiple Slack workspaces, notification settings are partially per-workspace and partially global. The “Notify me about” setting in Preferences is typically per-workspace. You might have “All messages” for your main workspace but “Nothing” for a secondary one.
Check: switch to each workspace (left sidebar icons) → Preferences → Notifications → verify the setting for each. It’s common to set notifications off for a community or side-project workspace and then forget — meanwhile it looks like “Slack notifications aren’t working” when really that specific workspace was deliberately silenced.
Slack also has a global “Pause notifications” mode in the top-level account settings (separate from individual workspace DND) — if this is active, all workspaces are silenced simultaneously.
Slack desktop app vs browser Slack
Some companies use Slack in the browser rather than the desktop app. Browser Slack sends notifications through the browser’s notification system, which requires separate permission.
For Chrome: chrome://settings/content/notifications → confirm slack.com is in the “Allowed” list, not “Blocked.” If it was blocked when Slack first asked for permission: go to app.slack.com → click the lock icon in the URL bar → Site settings → Notifications → Allow. You may need to reload the Slack tab after changing this.
Browser Slack notifications also require the browser to be running (at least in the background). If Chrome is closed, Slack-in-browser notifications won’t appear, even if Slack would normally send them. For this reason, most Slack users prefer the desktop app — it handles its own notification delivery independently of any browser.
Presence and away status
Slack distinguishes between “active” and “away” status. When you’re marked as away, Slack’s desktop notification behaviour changes — by default it routes some notifications to mobile instead of desktop. If you’ve set yourself to “Away” manually (click your profile picture → set away status), desktop notifications may behave differently than when you’re “Active.”
Also: Slack automatically sets status to “away” after 30 minutes of inactivity (no mouse or keyboard in Slack). If notifications feel like they get quieter in the afternoon when you’re less interactive: this could be why. The setting “Use different settings for my mobile devices when I’m not active on desktop” in Preferences → Notifications controls this specifically.
| Issue | Likely location | Fix |
| No notifications from any channel | Slack DND on, or Windows Notifications off for Slack | Check bell icon; check Settings → System → Notifications |
| Specific channel is silent | Channel muted or set to “Off” | Right-click channel → Unmute; adjust channel notification setting |
| Banner appears, no sound | Volume mixer or Slack sound setting | Volume Mixer check; Preferences → Notifications → sound on |
| Works in DM, not in channels | Notify me about = “Direct messages only” | Change to “All messages” or add keywords |
| Only morning notifications, none later | Notification schedule cutting off | Preferences → Notifications → schedule → disable or extend |
| Multiple workspaces, partial silence | Per-workspace setting differs | Check Preferences in each workspace separately |
Slack notification problems are rarely a bug in Slack itself — they’re almost always configuration. The most common scenario I’ve seen: someone sets up a notification schedule for work hours, forgets about it, then can’t figure out why they’re not getting notifications in the evening when they work late. The bell icon check and the Preferences → notification schedule are where to look first.
Slack app restart and update
Sometimes Slack simply gets into a bad notification state — the app is running but the notification delivery path is broken internally. A full quit and restart often clears it:
Right-click the Slack icon in the system tray → Quit Slack (not just close the window — that minimises Slack to tray; you need to quit). Wait 5 seconds → reopen. Test notifications.
Also check for pending updates: Slack → Help → Check for updates (or it usually shows in the menu if updates are available). Notification bugs in specific versions are patched regularly. Running an outdated version is a common reason for persistent notification issues that users can’t resolve through settings alone.
Keyword notifications
If you don’t want every message but need to see specific topics: Preferences → Notifications → “My keywords” → add terms that should trigger a notification when mentioned anywhere — your name, a project name, a product you support. Keyword notifications are particularly useful for large, busy workspaces where “All messages” would be overwhelming.
Keywords are workspace-specific. Add them in each workspace where they’re relevant. They appear highlighted in yellow in the channel view and trigger a notification even if you haven’t been directly @-mentioned.
Notification grouping behaviour
Windows 11 sometimes groups multiple Slack notifications into a single banner if they arrive in quick succession. Instead of seeing five individual message banners, you see one “Slack — 5 new notifications” summary. If you prefer individual banners: Settings → System → Notifications → Slack → “Show notifications in notification center” is on but Action Center grouping can be adjusted per-app (limited in Windows 11 compared to older versions).
For teams using Slack heavily: grouped notifications are actually more useful. The Action Center shows all pending Slack notifications when you click it, grouped by channel. Clicking the group opens Slack directly to the oldest unread in that channel.
Corporate Slack enterprise plans
On Slack Enterprise Grid (used by large organisations), admins can configure notification defaults and restrictions at the organisation level. If your Slack is enterprise-managed, some notification settings might not be configurable by individual users. The settings page would show “Set by your administrator” for locked options.
In enterprise environments: contact your Slack workspace admin if notification settings appear greyed out or you can’t configure what you need. They can adjust org-level policies or grant user-level overrides.
What actually works most often
For most “Slack isn’t notifying me” complaints, the resolution is one of:
- Notification schedule was on and cutting off notifications after work hours
- Windows notifications were disabled for Slack at the OS level
- A specific channel was muted (and the user forgot they’d muted it)
- Slack’s own DND was active and no one noticed the bell icon had a slash through it
None of these take more than 2 minutes to fix once identified. The test-a-DM-to-yourself approach quickly confirms whether the full notification pipeline is working or whether there’s a specific scope of silence (all of Slack vs one channel vs sounds only). Narrow down the scope and the fix becomes obvious.
Tips for staying notified in busy teams
Once notifications are working again, a few practical setups to keep them manageable:
- Use “Only mentions” for high-traffic channels you need to follow but don’t need every message from
- Star important channels — starred channels show at the top of the sidebar and bold-count unread messages even when notifications are set to “Off”
- Use @here and @channel sparingly yourself — they override per-channel notification settings for members, which creates the expectation that these pings are actually urgent
- Slack’s “Remind me” feature (three-dot menu on any message) lets you snooze follow-up to a specific time, reducing the need to constantly monitor for new messages
Slack notifications work best when they’re configured intentionally rather than leaving everything at defaults. The default “All messages” setting in large teams quickly becomes overwhelming, which leads to people muting everything, which leads to missing actual important messages, which is what brings them to troubleshooting guides like this one. Spending 10 minutes configuring per-channel settings properly saves many hours of missed notifications — and annoyed colleagues — later. See also Slack Notifications Not Working for a related case.
