I recently learned about a situation where someone in my department had a Teams meeting with a potential business partner. After the call, one of the participants received an unsolicited LinkedIn message from someone on the other side. It got me thinking about privacy. What are some effective ways to ensure anonymity during these meetings? Is there a solution other than using a locked-down generic account for Teams that limits interaction? I know there's an option for participant anonymity, but it seems like the host or organizer can't be anonymous. Any ideas?
4 Answers
Honestly, I think this is more about managing people than fixing any tech issues. If someone feels uncomfortable receiving messages after a meeting, that’s something that needs to be addressed on an individual level. Tech alone won't solve this problem.
Look, unsolicited LinkedIn invites happen to everyone, regardless of appearance. It’s just part of networking. Unless the invite had inappropriate content, I don't really see it as a major issue. If it was something inappropriate, she should definitely report it, but otherwise, I think people are just trying to connect for business opportunities.
But isn't it a good practice to protect your team from unwanted attention? It can be intimidating to get those invites, especially for those who might not feel comfortable.
You could have the guest join the meeting without using a personal account. Just have someone from your organization start the meeting. But I heard that might require a specific Teams license, which is a hassle. You're trying to keep licensing under control, right?
Exactly! It’s frustrating when you’re trying to simplify things but run into barriers like licensing.
If I’m being honest, every single person gets these LinkedIn requests all the time. I think it’s just a part of the job, no matter who it is. Plus, wouldn't this be an issue regardless of who received the invite?
The issue seems different depending on who receives the message. People have different comfort levels, especially in a workplace context.
I totally agree! It seems like a communication issue that needs to be handled internally rather than a technical glitch.