Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.

Five types of public/privacy that is being asked for by users:

- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)

LOG INTO MULTIPLE ACCOUNTS
Original user posted:
I would like to heave this multi-team/tenant option within “MS Teams”, like in Slack. Currently I’m in four different organization. They’re using all office365, three of them now changed from Slack to Teams. I’ve to permanently login/logout to switch to the related MS Team. This is really time consuming.

Another user says:
We need the ability to sign in with multiple accounts. Many of us have several O365 accounts for various reasons (consulting, etc), and we’d need to be able to access teams directly.
This is not a federation or B2B scenario, but a case where new O365 credentials have been created in another tenant for us. The app today only allows a single signed-in account at a time and that’s a blocker.

SHARED CHANNELS ACROSS TEAMS
From a merged idea:
Please add support for shared channels which could be used in multiple teams. Suppose there is one company-wide team with multiple channels. It would be great if all teams within the company could include these channels or at least one of them in their own team. In that way you don’t have to recreate the channel for every team again.

Quotes from various users about memory usage and slow performance:

"Team is a memory hog! 100s MB! Slack is about 50."

"The memory consumption is over 300MB!!! This should be a priority."

"Just started evaluating teams, 500+ MB and 10-15% CPU. This is in a citrix VDI. Does teams use hardware rendering? If so is there a way to turn it off? I had to do this with the rest of Office."

"I dont understand why my Teams application only uses 70MB when other people in my organization are towards half a gig! What is causing this Teams?"

"Make it less CPU heavy, 20% CPU on switch tabs? Really?"

"See attached picture."

#1 User Request on SharePoint:
Enable integration of Microsoft Teams to an existing SharePoint site rather than to always create a new site collection

There have been a few ideas raised on integrating lists, OneNote, document libraries, etc. from an existing SharePoint site with Microsoft Teams, but in summary, it will be best if we could create a team upon on existing site, so that the "Files" and "Notes" tabs would directly reference the existing document library and OneNote in SharePoint. It does not make sense to have two separate sites: one for all the usual SharePoint stuff, and another just for Microsoft Teams.

#2: Link to Existing SharePoint Sites

Trying to link my Team up to an existing SharePoint site - only seem to be able to link to individual folders rather than the whole document library, meaning that if i want all folders on the Team i need to create multiple tabs to get this. Would be good to link to a whole document library rather than one folder.

#3: Other Asks

Post Team chat to SP microfeed
Connect team sites onenote if available (replace default notes)
Add links to existing document libraries (replace default files)
Add links to existing lists
Add support for SharePoint taxonomy and managed metadata, SharePoint views etc :D