How are others here managing notifications in this...
# give-feedback
t
How are others here managing notifications in this workspace? I am not able to disable notifications for some of the noisier messages that include
@everyone
or
@channel
. My next best option might be to disable notifications entirely, but I’m wondering if others have found a better workaround? This isn’t my main workspace and I like to use slack notifications to be informed about things I absolutely need to look at. This is great for threads I’m in or @mentions. However, being able to avoid notifications for the blast outs is important when participating in multiple secondary workspaces like this one. Open to feedback!
plus1 1
image.png
u
Hi Tanner, appreciate your feedback. Currently, only admins can use
@everyone
in #C01A4CAP81L on Slack. When enabled, users can’t disable notifications. We use it sparingly for important updates. I’ll share your feedback with the team to explore improvements.
t
I appreciate the response! This is all coming from a place of trying to be helpful. It seems odd that workspace settings dictate that I cannot opt out of notifications for
@everyone
etc. And maybe it’s just me, in which case I’m ok going as far as disabling notifications. But for example, today’s announcement was calling for beta testers for
mssql
, which I imagine is a small fraction of the users here and begs the question: why am I not in control of how I’m being notified for this? Your #C01A4CAP81L channel is the global channel (default’s to #general in new workspaces). People cannot leave it. Further:
[@everyone] will notify everyone in the #general channel whether their availability is set to active or away. (<https://slack.com/help/articles/202009646-Notify-a-channel-or-workspace
|source>)
So perhaps another option would be to rename #C01A4CAP81L to something more general and create a dedicated #C01A4CAP81L channel that people could opt out of if they don’t care for the blast outs.
Turns out that setting my notification preferences for #C01A4CAP81L to
Nothing
didn’t help,
image.png
u
Hey Tanner, thanks for your valuable feedback. It sparked an internal discussion on how we handle announcements. Sorry for another one today. We’re working on improvements, the plan is to consolidate all info into a single announcement to make it more focused on important topics.
👍 1
t
No need to apologize for it, especially if this is how you intend to use Slack as a medium for communication! I was mainly looking to see if other’s had suggestions on how I could tune my Slack settings, but “two birds one stone” as far as also getting feedback to you and the team.
airbyte rocket 1