This feature request has moved to the planning stage. There have also been several small updates that have gone out already, as well.
I’ll keep you posted as I hear more about coming updates.
Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
Listen, channels should never have had just a folder in the default doclib to begin with, they should each have their own doclib instead. This would have made things much simpler!
The general channel could have used the default doclib and anything you put there would have been immediately visible from Teams.
No more confusion as to why folders created in the root in SharePoint aren't visible in teams. No more confusion as to what those folders belonging to teams channels are doing in SharePoint.
And no more confusion regarding renaming channels and corresponding folder folders. Now you do get a new problem as renaming a doclib is no simple matter if it means renaming the URL and people are syncing it using OneDrive, linking to it, etc. But that's another discussion.
I encourage people to go vote for this feature if they agree:
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
Very hard for users to understand that this is not possible - especially when they're used to do this in Dropbox, etc.
We need it for private Microsoft Accounts too.
This feature request is still being reviewed by the feature team. No new details to share at this time.
I frequently observe people clicking on the team’s name expecting to see content, instead of it expanding/collapsing channels. I think people think of it like file explorer, where any folder you click has its own content, and if you want to expand/collapse you click the little icon.
So I’ve often thought that a dashboard of sorts would make much more sense. The most obvious way to do this, to me, would be to just show the home page of the underlying SharePoint site.
Obviously that page would need to be changed a bit. But it already needs some work anyway, since there isn’t an obvious way to get to the team if you somehow end up on the SharePoint site. The homepage needs a way to go directly to a certain channel in the team, for instance.
By having separate libraries for each channel you also get these benefits:
- Easier to have separate permissions for each channel and even sharing settings
- No more folders in the default doclib that confuses people, especially when they get renamed, deleted, etc
- Makes it possible to associate the default doclib with the general channel so everything that is created in the SharePoint default doclib can show up in Teams, unlike today where people are confused as to why their content sometimes doesn't show up.
With this it should of course become possible to:
- Reassociate an existing channel with a new doclib and move its content to the new doclib
Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.
Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
We are still considering this feature for future releases, and will continue to update the status when it changes.
As we announced at Microsoft Ignite 2019 this morning, we are excited to confirm that Multi-window capabilities are coming to Microsoft Teams, and will start rolling out to the public ring early next year!
Alex & the Teams team
Teams has so many features packed into one interface, we need to be able to open up things separately. Not only chat, but also documents, tabs, meetings, planner, etc.
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
IT Admin’s now have the ability to configure apps on the left navigation of Microsoft Teams. You can learn more about that feature here: https://docs.microsoft.com/en-us/MicrosoftTeams/teams-app-setup-policies
As announced at Ignite we are currently working on enabling desktop users to add personal or favorite apps to their own left navigation.
As stated in the last update, the ability to use multiple Teams accounts at the same time is being implemented in stages for Desktop. Faster tenant switching functionality on the Windows client has been rolled out to the public ring fully, and Mac will begin rolling out soon. Work is in progress on cross-tenant notification improvements, and support for multiple accounts on desktop will follow. We’ll keep you posted!
Note: The ability to use multiple Teams accounts at the same time is supported on iOS & Android today.
Alex & the Teams team
Thanks to everyone who volunteered for testing the Office 365 group calendar. The TAP team will be reaching out as we are closer to being ready.