Loading tutorials…
Loading tutorials…
The default Slack notification settings are designed to be engaging. That's the opposite of what a focused marketing team needs. This is the configuration that lets people stay reachable without being interrupted.
Who this is forAnyone whose Slack pings them more than 15 times a day on focus work. Also marketing leads setting workspace-wide notification defaults so new members start sane.
What you'll need
Step 1
Slack → your profile picture (top-right) → Preferences → Notifications. Set "Notify me about" to "Direct messages, mentions & keywords" (not "All new messages").
Click your profile picture (top-right) → Preferences → Notifications.
Under "Notify me about new messages...", select "Direct messages, mentions & keywords." This is the focused default.
"All new messages" is the firehose — only use this for channels where every message genuinely needs your attention (which is almost no channel).
"Nothing" is for vacation. Use the Do Not Disturb scheduler instead — it pauses notifications cleanly.
Step 2
In Preferences → Notifications, scroll to "My keywords." Add 5-10 keywords that you want to be notified about anywhere they appear.
In Preferences → Notifications → "My keywords."
Add: your name (and nicknames), your company's brand name (so you catch every mention), your active project names, your top 2-3 client account names.
Use sparingly — every keyword is a notification firehose. 5-10 is the practical maximum.
Pro tip: add the names of competitors and important industry terms only if you specifically want real-time pings. For monitoring, build a Slack AI digest instead.
Step 3
Right-click any channel in the sidebar → "Change notifications." Override the workspace default per channel.
Right-click a channel in the sidebar → "Change notifications" → choose: Default, All new messages, Mentions, Nothing.
For #announcements: "All new messages" — you want everything.
For #social-random: "Nothing" — opt-in browsing only.
For #ops-* (integration firehose channels): "Mentions" — only if someone tags you.
For #team-marketing and #project-* you actively work on: "Mentions" or "Default" depending on your role.
Step 4
In Preferences → Notifications → Do Not Disturb. Set a daily schedule (e.g., 7pm-8am) so Slack stops pinging after hours.
Preferences → Notifications → 'Set a notification schedule.' Toggle on.
Set 'Allow notifications' window (e.g., 9am-6pm). Outside that window, Slack queues notifications silently.
For weekends: select "Different settings per day" and set Saturday/Sunday to "No notifications."
When someone @channels in the middle of the night, your phone stays silent. They will see "Do Not Disturb" on your profile and decide whether to override (only @channel with the "Notify anyway" option).
Step 5
In Preferences → Notifications → "Notification timing on mobile." Set mobile to mentions-and-DMs-only so your phone is quieter than your laptop.
Preferences → Notifications → "When I'm active in Slack" and "When I'm not active in Slack."
On mobile, set "When I'm not active" to "Mentions & DMs only." Desktop can be more permissive because you control attention while at your desk.
On mobile, also set "Send notifications about" to "Mentions and DMs only" globally. The phone is the worst place to firehose.
Most knowledge workers should have desktop "all selected channels" + mobile "mentions and DMs only." That split protects evening and weekend focus.
Step 6
Some channels deserve a visible unread badge; others do not. Configure per-channel so the sidebar tells you what matters at a glance.
Right-click any channel → 'Change notifications' → 'Include this channel in your unread badge count.' Toggle off for low-signal channels.
Goal: your unread badge should show 0-3 channels at any time during the workday. If it shows 15, your notification config is too loose.
Star the 5-10 channels that deserve permanent top-of-sidebar visibility. Star = priority anchor; notification = interruption. Different controls.
For #social-* and #ops-*, exclude from unread badge. You'll browse them on your own time.
Step 7
After configuring, run a week. Track notification volume (Preferences → Notifications → "Notification summary"). Tune.
Slack tracks how many notifications you got per day. Look at the trend after one week of new settings.
Target: under 20 actionable notifications per day. Past 40, the team starts to ignore Slack and you lose the system.
If you are still over 40 after one week, the next lever is keyword cleanup (too many keywords = firehose) and channel pruning (leave the channels you do not need).
Repeat the audit quarterly. Notification volume tends to drift up as new integrations and channels are added.
Common mistakes
Keeping "All new messages" as the default
What goes wrong: Slack interrupts you on every channel message. Average knowledge worker loses 90+ min/day to context switching. At $50/hr loaded cost, that's ~$60/day, ~$1,200/mo per person. Multiply by team size.
How to avoid: Set default to "Direct messages, mentions & keywords." Override per-channel for the rare channels that need every message.
No keyword notifications
What goes wrong: Your name gets mentioned in a channel you are not active in. You miss it for 2 days. Decisions move forward without you. Cost compounds — a single missed mention on a $20K deal is the whole annual cost of Slack Pro for a 25-person team.
How to avoid: Set 5-10 keywords in Preferences → Notifications. Include your name, brand name, active project names, top client accounts.
No Do Not Disturb schedule
What goes wrong: Slack pings at 11pm. You see it. You think about work. Sleep degrades. Compound effect: ~10% productivity drop the next day. Over a year, ~$5,000/mo in lost output on a 10-person team that has no DND norms.
How to avoid: Set Preferences → Notifications → Do Not Disturb to 7pm-8am weekdays, no notifications weekends. Set workspace-wide default if you are admin.
Same notification rules on mobile and desktop
What goes wrong: Phone pings on every message you would get on desktop. Evenings and weekends become reactive. Family time interrupted. Burnout accelerates. Average mobile-notification-fatigue cost: ~30% likelihood of churning a team member in 18 months.
How to avoid: Mobile = mentions and DMs only. Desktop = your normal settings. Different surfaces, different rules.
Notifications enabled on integration firehose channels
What goes wrong: #ops-hubspot fires 200 times a day. You leave notifications on. You check Slack 200 times a day. Productivity drops. The integration was supposed to save time, not steal attention.
How to avoid: Set #ops-* channels to Mentions only. Browse them on your own cadence. Use Slack AI daily recap to catch the signal without the noise.
Setting it once and never revisiting
What goes wrong: Notification config drifts. New channels join. New integrations get added. Six months later you are back to firehose, but it crept in slowly so you never noticed. Productivity has been bleeding for half a year.
How to avoid: Quarterly notification audit. Open Preferences → Notifications → review the channel list. Prune. Recalibrate.
Recap
Done — what's next
How to set up Slack channel conventions that survive team growth
Read the next tutorial
Hand it off
Notification configuration is a per-person task, but the team-wide pattern is a marketing-ops project. A growth-ops specialist on EverestX will run a 1-on-1 notification audit with every team member, configure mobile and desktop separately, and document the team default. Typically 6-10 hours at $14-16/hr — pays back in hours of recovered focus per person per week.
See specialist rates
Yes — right-click any channel → 'Change notifications.' Choose Default, All messages, Mentions, or Nothing. Mix and match: 'all messages' for #announcements, 'mentions only' for ops channels, 'nothing' for #social-random.
Keywords only trigger in channels you are a member of. If your keyword is mentioned in a private channel you're not in, you don't get notified — by design (privacy boundary).
Yes — when sending a DM during someone's DND, Slack shows 'They have notifications snoozed' and offers 'Notify them anyway' button. Use sparingly. For urgent ops, set up a paging system outside Slack (PagerDuty, Opsgenie).
Slack queues notifications silently. When DND ends, you get the 'You missed X notifications' summary. Nothing is lost — just delayed until you're ready.
Sound is the most disruptive form of notification. For most knowledge workers, silent (badge-only) on desktop and vibration-only on mobile is the right floor. Reserve sound for genuine emergencies (your on-call setup, not Slack).
Slack
Most Slack workspaces die not from low adoption but from too much adoption with no rules. This walks through the channel-architecture decisions that survive the jump from 10 to 50 people.
Slack
Slack has 2,600+ integrations in the App Directory. Most teams install 30, get hammered with notifications, and turn most of them off. This is the structured way to pick, install, and govern integrations.
Slack
You have 240 channels. Half are dead, half have unclear names, and search returns 30 irrelevant results per query. Here is the cleanup sequence that does not break the team.
Slack
Most teams treat Slack like a chat app — until it becomes a system of record, an integration hub, and a meeting replacement. At that point, governance becomes a real job. Here is the honest framework for when to hire someone to own it.