Hundreds of people, including all the senior managers and even the CTO! I checked the meeting invite in my sent folder and realised it had gone out to the entire department. I realised something was wrong a few moments later when I started receiving out-of-office responses from people I didn't recognise. And so I sent out the meeting invite, thinking it would only go to one colleague (the only one I had selected as a participant). I didn't realise this was an optional field, so I just selected the General channel in my department's Teams channel. I saw that Teams was asking me to select a channel. I needed to set up a one-to-one Teams meeting with a colleague, so I hit the 'Schedule meeting' button, added my colleague as an attendee, filled in the meeting name, date and time. This reminds me of something that happened to me a couple of years ago, near the start of the pandemic and when we had recently switched from Skype for Business to Microsoft Teams. I didn't realize it until a co-worker sent me a private message asking why I had just tried to fire everyone at our company.

So I dismissed it.īut I had accidentally sent it to my company's Slack organization instead of the hackathon-specific one. This didn't surprise me because attendees came from various countries for the event. Slack gave me a dire warning that my message would send notifications to so many people across so many time zones. When you are done with your work today, please delete all the data from your machines. 'Thank you everyone for contributing to our shared mission. The message I posted to #general (the channel everyone in a Slack organization is required to be in) with tagged was something to the effect of: At the end of the event, I was supposed to ask all attendees to delete all the data we had given them before they went home.

We created a Slack organization just for the occasion. Remind me of when I once helped organize a volunteer hackathon with people from different companies.

Github universal mailer