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.

#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

CHANGE PROMPT:
Change "Add team" to "Add or join a team": I avoided this button because I thought it would always create a new team. It wasn’t evident to me that I could browse for existing teams there too.

PREVIEW A TEAM:
Provide the ability to preview a Team without immediately joining, to see what the reason for the Team is and what Channels exist. It’s a little cumbersome to have to join, realize the Team isn’t what you thought it was, and leave.

TEAMS DISCOVERABILITY
Presently you have to know the name of a team to be able to search for it, if I am new to the company and I want to have a look to see what teams there are within my organisation I can’t currently, as I don’t know the names of them in the first place, it would be better if all public teams were visible.

Right now the conversation tab is the default landing page for a Team and/or Channel.
I want to be able to have a SharePoint site landing page in a tab and that tab be the default tab open when you navigate to a team or channel.

Think of it like a landing page for that team. You may not want it to drop right into Conversations. If you can have a SharePoint page with a Microsoft Teams conversations web part, you get the best of both worlds.
I can see a lot of scenarios where you'd want the chat window open and another tab at the same time. Rather than having to context switch. Imagine the SharePoint page tab being the way to do that by using Web Parts on a dashboard. A web part for the Microsoft Team and another web part for whatever was in another tab.