Eliminate "Context" Switching from Guest Feature
The new guest feature is a great start, but it feels more like a bolt-on than a core part of the experience. I'd like to see you be able to converse/collaborate as a guest in other organizations without needing to switch between tenants.
Each context switch takes several seconds and is disruptive, I know I'm being picky here, but I believe this would help keep the end user experience smooth and drive adoption.
Matt Shannahan commented
B2B collaboration is ready to explode in use. This needs to be fixed ASAP! You copied Slack a lot already, what is keeping you from copying this feature? We have dozens of clients on O365 with Teams that want open channels with us and we can't offer it yet due to this poor user experience.
I believe this could be merged with this suggestion and get 500+ votes and maybe some more attention from Microsoft?
Yes! The current functionality moves guest users to a worse position than "external" users. In some cases I've gone in and had to delete the guest user so that we could chat as just an external user. Problems with the current scenario:
- When I send a message to an external user they get it right away. A guest user won't see that I sent them a message, as far as I've tested, until they switch into my company context. That's odd.
- I can't see presence of a guest user like I can with an external user, unless that guest for some random reason switched to our context... in which case they no longer see notifications from their own company.
So although guests get a bit more access, and functionality in chats, they're a lesser citizen in day-to-day operations. Worse, I've started using Teams to chat with main site contacts at my customers. Then one day I go and share a spreadsheet from SharePoint with them. Now they're a guest user and I can no longer chat with them nor call them because they don't know they have to switch to my context on their end.
So either I never share files with external users and keep them as external users, or I share files and never chat with them nor call them in Teams anymore.
The switching would be less painful if it did not enforce the end of calls. Ever-so-often after ending a coordination call as guest of an external partner, I will call back the internal colleagues who also participated, to re-iterate on the meeting that just ended. But we cannot access the files and comments from the previous call, because it's in the other context.
John Howell commented
Please eliminate this need to switch. It seems to serve no practical purpose.
One of the major issues with switching is the "offline" status for guests.. they're uncontactable as soon as they switch to their primary organisation until they notice the tiny circle notification up the top 😒
DAVID J SASSANO commented
as a simple intermediate step, can you at least place the drop down used to switch orgs directly over the Teams on the left. Making it more visible when you are looking for the other orgs team will at least feel more integrated, and give you a quick visual clue as to which org you are in without scanning all the way over your screen.
Rob Macfarlane commented
Another alternative (if the UI can't be redesigned to show Teams from multiple orgs) would be to allow having multiple Teams windows open, one for each Org. Obviously this would only work on desktop.
Jakob Nøtseth commented
As a collaboration consultant, this is probably the hardest selling-point of Teams. This really needs to improve before making the hard move from Skype clients for chat, already a painful experience for all external project teams, not to mention all multi-tenant enterprise-organizations. As a consultant, I also try to use what I preach, which means using Teams for meeting invitations. Having to remember to place Teams in the correct home tenant before being able to use my own meeting link in the invitation is just crazy. Having to tell potential customers about this is just dumb. Get a grip Microsoft!
That isn't the only issue, the notifications that you might be missing something in a guest is very small in the UI. Bring guest access teams into the main UI!
David McKnight commented
Having to change tenants to use the features of Teams is the primary reason we have been slow to deploy to our clients. They are not going to think to switch to our tenant to check to see if there is anything worth looking at -- they need to be proactively notified to look (and the little number above the tenant switch is not it). They need to get a banner that says a message has come in, or an @mention is there -- or there is other activity in a channel they are following. Without this, the collaboration promise falls way short.
need an update on this MIcrosoft, this continues to separate you horrifically from Discord, Slack, etc. Discord has 'servers' and switching is relatively straight forward, and you can get some level of notification from other servers if your looking at another. maybe call it "Org"s and have it be a set of icons in the top bar? like an icon for my main org and next to it an icon for my 2nd org (I know that will get messy when theres more orgs, but dear lord, start with something!)
This would be extremely useful, please prioritize the implementation. Thank you!
Constantine Sulema commented
This is probably the most critical issue for the cross-org collaboration.
Bryan Heindel commented
Slack has handled this since day one, and Microsoft is 3+ years into Teams and still has yet to implement these crucial features.
My and my customers LOVE Teams...but the "by design" barrier of having to "switch" between federated chosen external tenants is a DEAL BREAKER! In Skype for Business me and my customers can chat with anyone. Why would I endorse a move from Skype for Business, where we and they CAN chat, to a Teams-only environment where they can send a chat to me, and it appears to have been sent, but I will only become aware of their chat IF a switch to their tenant takes place? It would be better to PAUSE any further marketing of Teams (as a replacement for Skype) until customers are responsibly informed of the DIRE CONSEQUENCES of this limitation. It renders Teams useless in the real world.
This is the most painful aspect of Teams!!
Our company, like many others, has plenty of partners. When you get added to their tenant as a guest it is just one more place you need to check for messages. The message indicator between tenants is like 25% reliable. The time to switch is awful.
And how about when you forget to switch back to your default tenant? A lifetime of collaboration goes by as you tunnel vision into whatever it is your working on at the moment.
We really need this one.
Not getting alerts from teams were you are a guest and constant tenant switching makes B2B guest access very difficult to use and to sell.
I hope this improvement finds it way into teams very soon...
Any news?? We constantly work with external partners and cross-company teams. The current method of dealing with guest users is horrible.
Robyn Bredvick commented
Please make this happen as soon as possible! It would be a huge benefit in time saving and complaints from my users. I have tenants that work closely together and I get complaints daily about this issue.