Hacker News Reader

Comment by magicalhippo | Hacker News Reader

We use Teams at work, and for that it works quite well. Calls and desktop sharing work well, the channels do what they do, integration with OneDrive and the wiki thing is nice etc.

But then I got a member of a different Team, for one of our customers, as part of some integration work. And boy is that a CF.

Unlike Discord you either have this team or that team active. Notifications from the other are horribly unreliable, and there's no way to chat with someone in one team while you're in a call with someone from the other team besides running a separate client.

So as such, "Teams" really should have been named "Team".

View on HN

Shameless plug. AirSend (https://www.airsend.io) offers the bare essentials one need to collaborate with both internal team members & external clients in one elegant package. Collaborating across organization boundaries is really hard with both ms teams and slack. Thats the problem we are trying to solve with airsend.

AirSend gives you a few simple (chat, voice/video, files, tasks and wiki) but powerful tools and then get out of the way.

>>and there's no way to chat with someone in one team while you're in a call with someone from the other team besides running a separate client.

This was largely fixed, you may have to enable the "new meeting experience" though, which starts your meeting / call in a separate window from the main client

I have that enabled and I still get the message that my call will end when I try to switch teams while in a call.

Last tried this a couple of days ago.

I am not sure what you mean by "switch teams". Are you attempting to Switch Tenants?

Guess I'm using the wrong words. To the left of my user name, next to the minimize/maximize buttons, I can switch (in my mind)... something. I guess tenant is the word, but in my mind that is the team.

I see now that what I've always thought of as "channels" is called Teams, no idea how I've overlooked that for over two years but there you go.

My point is in Discord I can be on a dozen different servers with different administrators and seamlessly go between them. Not so in Teams. I'm stuck to one tenant (team) at a time. Which sucks if you need to switch between them.

I see, I am not sure how common that is. Most places you only need 1 Tenant unless your are contracting with Multiple companies but even then you would be set up as a Guest on their tenant not have your own independent user name for each tenant you need access to.

You are correct that Teams today does not support Multi-Tenancy but that is really not an issue for 99.5% of organizations who would only ever have 1 tenant anyway

Teams is structure as

Tenant -> Teams -> Channels

Yeah I guess it's a bit different since we're so heavy into complex integrations with our customers.

Anyway, up until this became an issue, Teams has worked quite well. It does what we need when we need it, so can't complain really.

Reply on news.ycombinator.com