11-03-2016 02:17 PM
11-04-2016 12:54 PM
11-05-2016 08:45 AM
01-30-2017 10:59 AM
01-30-2017 10:59 AM
I agree! Otherwise, it will be necessary to create diferent groups to manage the acces.
03-22-2017 08:12 PM
I dont see it as much important for limiting access, but being able to have members for a channel, so that you can have topic relevent discussion, and call people to a meeting without everyone in the entire team being notified. We have a project with 250 people in it, and dont want to have to have a separate team for every "sub-team".
03-23-2017 04:24 AM
03-23-2017 06:45 AM
You can sort of do that now. Many people don't realize that the favoriting mechanism for channels controls more than just their display underneath your Team. It also controls whether you get notifications when someone @ mentions the channel itself. If you have it favorited, you get a stronger form of notification (a toast and the red badges/icons I believe) where if you don't have it favorited the channel name just goes bold to show that activity has occurred.
06-21-2017 03:37 PM - edited 06-21-2017 03:38 PM
This one sounds familiar. Having the same dilemma at the moment also... Creating so many "Teams" just to have contextual coversations and events. Team of 25 working on same product/cliente that work in sub-teams (e.g. 5 scrum teams), should I create 1 MS team or 5 MS teams. If I could use 5 channels, 1 for each sub-team and then have common/other channels for full 25 members would this be better/easier to manage/maintain/use?
10-05-2017 12:34 AM - edited 10-05-2017 12:49 AM
10-05-2017 12:34 AM - edited 10-05-2017 12:49 AM
I too have been looking at limiting membership to specific channels, one of the reasons I feel this is importnt is we have set up overarching directorate teams, and each team that falls under the directorate has its own channel for their daily chat, wips and team admin.
The intention was to also hold team meetings with a single click within teams however when we do this it dials the entire directorate, over 100 people instead of the 10 in our team :(
Yes I know we can set this up in chat, but for some teams its important to have voice and text done in an open and transparent way, with an audit log to see when the calls were made.
10-06-2017 12:38 PM
We would really need that feature too. Would make it possible to structure a Team with Sub-Teams.
10-13-2017 09:47 PM
10-24-2017 05:20 AM
So far that I know, you can achieve that for the documents stored under that channel by opening the documents channel in SharePoint, then going to [Site contents]. Once there, click on ... next to Documents and then [Settings]. On that Settings page, select the [Permissions for this document library] link. Be sure here to click on [Stop inheriting permissions].
Once that done, go back to [Documents] on the left menu. You will get one folder by channel. Select the one you want to change permissions en click on the outer right icon next to the filter. It will open the details panel. Here, you are able to [Manage access]. You are able here to stop sharing for Team visitors and Team members.
You are now able to share ad hoc any of your AD's member.
10-24-2017 05:26 AM
@René Cuchetwhile your approach will work, it has many limitations and I would be very reluctant to recommend this to any of my clients because it will end up causing a great deal of confusion. The team members will still be able to access any of the other resources associate with that channel. The wiki, other tabs, connectors, conversations, notebooks etc will all still work and the team could be confused that they can't use the files.
10-24-2017 05:36 AM
@Dean Gross True. My meaning was only Documents wise and is only helpful in case of Team members synchronizing files on their computer. For sure that it can be confusing for Team members but is a good way to take care that some confidential documents are only shared with the right persons without making a apart Team for that.
I gave the example on a Channel level but in our case, I have implemented it on folders under a channel
01-13-2018 09:30 AM
@Graeme Baker wrote:
Is there any way to control which channels within a team each team member has access to? Or is it a free for all if you're a member of that team?
Are there any updates on this?
01-13-2018 04:38 PM
You can use PowerShell to have a look, which user are in which team. In combination with Azure AD/hybrid and some Workflows you can control it.
An option to connect Azure AD users to Groups/Teams: no
You have only: in or out / not a function like: this members can be a part, but are not members yet.
If you want this -> teams.uservoice
01-15-2018 01:28 AM
01-19-2018 12:48 AM
I absolutely agree and can't understand why Teams (a good product in concept) doesn't allow for channels to be restricted to particular members. Making a channel a favourite as a way of making sure people can focus on what pertains to them as members of a sub-team is a clunky solution.
01-19-2018 12:51 AM
Understand the frustration, I think Teams was just adopted and used in much more complex/deeper ways than Microsoft originally envisioned, where they saw it being an open space where there would be no private content within a Team, but as you say practically that isn't how it is working in the real world!
Rest assured they are working on it!
01-19-2018 01:12 AM
Much of the feedback and drive here would be more effective in the correct feedback forum. This item is the second most popular feature request on the Microsoft Teams User Voice Feedback site. As well as voicing your opinions and preferences here, please don't forget to pop over there, vote up the feature request, add your two pence (or cents); Support for Private Channels
03-19-2018 02:12 PM
The need of "sub team" could be in a client/customer relationship. I.e company A invites users from company B to a team. Company A is the "buying part" and needs to have some internal information within their team and only want to invite company B to some channels for collaboration.
03-21-2018 08:33 AM
05-04-2018 07:50 AM
In my case creating a team requires a request to enterprise IT and it does not make it a viable option to create multiple miniteams. So private channels would be so good.
06-06-2018 10:19 AM
I agree this would be helpful for my team as well. I hope that in the future we will be able to do this.
07-06-2018 01:22 PM
Agreed. If my team is working on a project for a client, and we add that client as a guest to see some team files in one channel designated for them. We don't want the client to be able to see files in the other channels. We Also don't want to have to create separate teams just for the gust access, or manually apply guest access to each individual file. Microsoft, if you want more people to adopt your technology, please add the features and usability that we actually need.
07-09-2018 07:12 AM
07-09-2018 07:15 AM
07-09-2018 07:17 AM
the only idea I have is to show Microsoft what's up in the only language they speak. $$$
when friends ask me about my Office 365 subscription I tell them exactly where it falls short, what promises were made and not kept. A few sys Admins I spoke to immediately reversed course on procuring 365 after one of those conversations. Once MS realizes that Slack and others are eating their lunch because of their own shortsightedness, maybe they'll pay more attention to their customers' needs.
08-03-2018 02:56 AM
It's pretty wild that this still isn't done.
Essentially limits the usefulness of teams and makes it only appropriate for the most superficial of things. Perhaps that's what they're going for but it would be good to be able to actually use it for real work.
08-03-2018 08:34 AM
08-03-2018 08:52 AM
I've found a way to have some folders and files within a Team channel that we can limit guest from being able to see them.
I haven't yet figured out a similar work around for the chat feature, but this is quite useful for limiting file access.
09-20-2018 11:29 AM
Hope is on the horizon (I hope). The response to this uservoice suggestion states they are actively working on it, as of August 2018.