This feature request is working its way through the backlog queue. No new details are available yet.
Hello Suphatra, hello all,
I believe that we started/voted this petition because most of us are working in/for a platform that already contains hundreds of sites (and in my case thousands sub-sites!). Some of them belong to departments existing for years.
I wanted to mention that my curiosity on this tool started at the moment that, as central support for SPO, an end user asked me about the best chat app to add in a site, something more dynamical than the good old discussion boards. I believe that Microsoft, after so many years of experience in chat applications, will find the best GUI to manage all generated conversations (historical, logs, search, apps for mobile devices and other OSs).
Hence, the scenario my company prefers is A rather than B, that we already tested and, as someone already said, may cause confusion.
As long you enable linking the creation of a new Team to an existing site or (remark) sub-site I don’t mind if, for the case, a new library is created to log all the activity related to the new team: chats, notes, calendar and documents by default.
And what about making feasible to link several new teams to a single site or sub-site then? In fact we are all claiming to link to an existing site, but what about if the site is already linked to another team?
(I’d like to remind that my interest to this awesome tool started at the moment I was looking for a chat tool to embed in an existing site and empower the users to use it from their mobile devices)
9/10 …then improve the GUI of the app for mobile devices that is too poor :-D!
Not sure about what you mean with the “Create Channels API”. In a quick search I could not find clear information about it; but I rather prefer something easy to explain to the end users of my company, directly in the webform at the moment to create a new team.
Blessings from Barcelona!
@Supathra, I agree @Isaac Chua's comment (a thumbsup is missing here). In fact I first voted the one he appoints.
To both requests I would add the possibility to give a SP Group the ID of a Team and save this way the need to different places to update arrivals and departures.
Indeed, SP was first and there are already many teams working around their shared workingspaces... making it easy would to extend a site with the current Team's new features... at end, be able to embed, among other things, the main chat timeline in a webpage.
Great to discover that we can add a SPO as a tab. However I agree with all those colleagues who wish to embed, show, add ... (whatever you want to call it) the timeline of a Team conversation in a SharePoint Page. By extension, maybe available already, to authorize users by adding the team ID at the security layout of any site.
I agree too with the comment of anothe colleague asking for a way to connect all the chat applications you already have (Skype, Groups, Slack, ... ) and get a single timeline. It sounds a bit Tolkien... but not in fact "...a ring to rule theme all" but connectors to have all what happening at a glance... something like what in Twitter when following a #tag but with the ability to post at all timelines associated (maybe this should be posted in another thread)
Adding any emoji as a reaction remains under review.
I am marking this as partially done to let you know a new reactions bar with Like, Heart, Laugh, Surprised, Sad, and Angry has begun rolling out to all users.
We are still considering this feature for future releases, and will continue to update the status when it changes.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.