Tanner Perrien
02/27/2024, 6:35 PM@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!Tanner Perrien
02/27/2024, 6:36 PM[DEPRECATED] Marcos Marx
@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.Tanner Perrien
02/27/2024, 11:41 PM@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.
Tanner Perrien
02/28/2024, 9:13 PMNothing
didn’t help,Tanner Perrien
02/28/2024, 9:13 PM[DEPRECATED] Marcos Marx
Tanner Perrien
02/29/2024, 5:31 PM