12-12-2018 09:08 AM
12-12-2018 09:08 AM
We are using Teams as our primary source of comms internally but we find that in a lot of instances we are having to create new teams, when a new channel with different permissions would do.
I know this is being worked on but are there any updates on the progress?
Identity Experts Ltd
12-12-2018 09:11 AM
Can you please elaborate on what you mean by channels with different permissions? Are you referring to private channels?
12-12-2018 09:15 AM
In a manner of speaking yes. We would like to have say, 30 people added to an over all team. But within that team have different channels that only a subset of these users can access.
This way it keeps the interface clean and easier to navigate. We would also love a channel under a team that we could limit guest access too. For example for this channel allow guests from this domain access for collaboration and meetings but keep the rest of the team off limits to them.
Hope that makes a bit of sense.
12-12-2018 09:21 AM
12-12-2018 09:24 AM
12-12-2018 09:26 AM
12-12-2018 09:28 AM
Private channels is a high priority for us - we are working on it. Stay tuned for more updates coming on this.
12-12-2018 09:28 AM
Private channels will enable you to have individual permissions for channels. We are working on that but I do not have an update for you as to timeline. If you'd like to "clean up" the user interface you can have people remove the "favorite" designation for channels. Those not favorite will go down into "More". I often do this when in a team with a lot of channels (best practice) that I don't have to stay on top of or aren't specifically relevant to me.
12-12-2018 09:31 AM
Our primary use case is we would like to restrict Guest access to specific channels within a Team. We currently manage 2 Teams per project. 1 Internal Team and 1 Guest facing Team. This duplicates work and causes lots of confusion. Obviously we don't want a Guest to have access to all of the channel chats and documents, but would like them to be included in the same Team...with restrictions.
12-12-2018 10:17 AM
12-12-2018 10:35 AM
We are doing something similar where we have to have two Teams to support one "audience" (team):
One Team is created for the overall group; another Team is created for the senior members (leadership, management, whatever). While I can argue that this is good because senior members don't need to worry about the files that are saved in the SharePoint site, I'm conflicted because I'm not a fan of having another location to store a single team's content.
12-12-2018 10:59 AM
12-12-2018 10:59 AM
12-12-2018 04:13 PM
03-27-2019 06:07 AM - edited 03-27-2019 06:08 AM
As of now 27th of Mar 2019, this is not possible yet. I'm sure MS Team is working on it.
However, there's a way how you can impose permission i.e. from the group site only.
1. create a site page and customize according to your taste. You can do many things on it as per the add ons.
2. assign individual permission. just check on the manage access.
3. customize your main group site and create a link to that site.
Hence, rather than using fully the MS Teams, you can either create a link on it or advise your team to access the main page.
Hope this help.
04-11-2019 11:30 AM
@Shruti Poddar - just came over to a midsize Microsoft shop from a smaller Slack + GSuite shop. This is a crucial feature. Just practically, in a matrixed and permeable organization, teams are typically not whole numbers of identical people. In the Product function, depending on product/project/activity, I may pull fractionally from other teams (design, architecture, etc.) or outside resources (UX, consultants, etc.) and involve external clients/partners. The default access control means I have to decide who to give all the Product permissions to...thereby limiting it to people who are active on all the things or executives. It limits the practical utility dramatically.
Related, an underappreciated aspect of Slack is its promotion of digital culture. Being able to throw up channels and self (de)select is big. That and being able to start private channels can foster certain types of sub-cultures (game nights, local events, conferences, interesting books/articles, etc.) and conversations. Having teams and chats just doesn't do the same trick.
Hope this is still very high on the roadmap/backlog!
07-08-2019 07:14 AM
Hi There @Shruti Poddar any update on this. Our company is planning a substantial investment in Slack Enterprise Grid as a direct result of Teams inability to deploy this? We have a complex organisation as channel permission is a must to prevent the need for 50 different workspaces.
07-24-2019 10:45 AM
we need this for sure. Often times where Managers need to discuss things in a management Team, then sub channels from there for specific projects and invite in guests (consultants, internal users, etc) that are NOT part of the full team but needed for this one project. No one wants to give out unnecessary group membership and access!
I have not gone thru and tried to play with tons of sharepoint permissions to see if there is a way to mess with it and fake it as that is far too much work and documentation. This should have been there from the beginning.
07-24-2019 08:42 PM
07-31-2019 09:27 AM
07-31-2019 09:42 AM
I just tried this yesterday and did not see anything like that for options. Do you have a link to some documentation on how to do it? I am assuming it will be some kind of powershell for a while before you do anything in the UI @bonfieti
07-31-2019 10:02 AM - edited 07-31-2019 11:56 AM
08-02-2019 01:03 PM
08-05-2019 01:40 PM
@TeamProMember definitely agree. I jjust created a new team and cahnnels in our current Teams environment and the Privacy option is not visible. See this recetn post on UserVoice for teams - 7/3/2019
08-20-2019 03:33 PM
@bonfietiI think you are referring to creating Teams... the same option, one level below, when you create Channels within a Team, is not available yet... not for us at least as of Aug 20 2019...
09-05-2019 04:18 PM
09-06-2019 05:00 AM
@bonfieti We're using Teams Windows client 1.2.00.22654 (just confirmed it is the latest download available), and of course the client should't affect the feature set, but I can promise you I do not have the ability to change permissions for distinct channels.
So, lucky you! I would love to get an update on the availability of this feature from someone on the Dev team at Microsoft.
Anyway, thanks for the update.