> Pro tip: set your notification settings to silent by default.
You're lucky that your company lets you treat Slack like an asynchronous e-mail inbox with multiple channels. If you have the luxury of ignoring Slack notifications until you're ready to respond, you're in a good place.
But your company isn't using Slack the normal way. The implicit expectation is that Slack is an instant messenger, and that you're expected to reply right now. That's why the default settings lean toward aggressive notifications, and that's why you need to take extra steps to turn them off.
Slack has been a powerful tool for remote work and distributed teams, but it's also an interruption factory by default. Before I left my last company, I routinely had 300-500 notification pop-ups per day as people shifted toward DMs and managers started abusing @channel to rise above the noise and get their answers ASAP.
What kind of company says you have to enable notifications? That's some serious micromanagement going on. I'm sorry to hear you had to endure that.
The company could just as easily expect you to be reachable by phone or email at all times.
I try to create a culture where most channels are like that, and only a few channels have an expectation of urgent / immediate replies. Then I turn on notifications for all messages in those channels.
This sounds a lot like an email thread.
Pro tip: set your notification settings to silent by default. I occasionally turn on notifications for our automated system alerting Slack channel, usually when I'm not actually at my computer.
One thing I do think we do as Slack users is rely on it too much as a general information dump: even with the history, stuff gets lost. Slack is no replacement for wikis or other more static information repositories, make sure you extract valuable knowledge out and put it somewhere more suitable (and findable).