01-29-2019 01:17 PM
01-29-2019 02:02 PM
01-29-2019 02:27 PM
Very interesting blog, I'd lost track of Private Channels and this was a great catch up and how this may actually hurt adoption because of the extra complexities. The picture you paint is very familiar and common I think, throwing in private channels into the mix could be rough!
I look forward to seeing how Microsoft might minimize these potential issues when this is closer to release.
01-29-2019 02:56 PM
01-29-2019 03:00 PMSolution
01-29-2019 05:50 PM - edited 01-29-2019 05:51 PM
This was a great read - so many great points you bring up - thank you!
02-03-2019 12:53 AM
Having to deal with file shares permissions requests for many years i can see how private channels can become a mess and then users will demand IT to fix it :) I think you have good points, but i also can see why others want to get private channels. Maybe MS shouldn't have channels and just teams to begin with..
03-25-2019 11:09 PM
I think the way to manage this, to ensure that IT doesn't bear responsibility, is to have a good governance framework agreed with the business, and have business buy-in to the process. If they are invested in it, then they will help to make sure it works successfully. The other part is quality of communications on how Microsoft Teams is managed. Creating a knowledge article on how to resolve simple permissions issues stops tickets from being lodged by the customer with IT. If ownership of individual Teams lives with the Team owner, then it will be the Team owner's responsibility to manage that Team. The knowledge article will direct them to speak to the Team owner.
03-25-2019 11:23 PM
03-26-2019 12:47 PM - edited 03-26-2019 01:28 PM
03-26-2019 12:55 PM
05-13-2019 08:36 AM
@adam deltinger - Great article, and I agree with your thoughts around the Admin challenges of maintaining proper security structure over time. I can't speak for the other folks clamoring for this, but my desire for this feature has less to do with truly needing "Private" channels, and has more to do with providing end users a clean and concise view of their world, and reducing the noise within our organization.
For example, if I am a resource who is supporting many different account teams on project based work, I would only be interested in receiving communication which is occurring in the specific Project Channels I am a member of, and furthermore would have no interest in seeing or having to manage favorites throughout this sea of channels. "@channel" mentions start hitting a more relevant audience, because it is managed (rather then the annoying back and forth of "did you favorite it?" ..."I don't think so? Where do I do that?") From an account manager perspective, I would want all of the conversations containerized within that project channel to speed through any issue resolution and/or clarification efforts needed.
So from my lens, allowing Unique Membership at the channel level would make communication groups far easier to manage, and while capturing persistent chat in a more logical and intuitive location than the separate "Chat" bucket. I don't care about file restrictions, as any sensitive data is captured, as you mentioned, in a separate Library with governed permissions. With the ability to link to disparate file locations, this becomes any easy thing to manage in my opinion.
I help a lot of teams with best practices and user adoption with Teams (and a lot of other tools in the O365 family), therefore I am currently a member of 28 Teams, and subsequently ~180 channels.....growing every week. I would love to be able to create a "Support" Channel and drop off the rest so the UI is clean when I fire it up each morning, which allows me to quickly identify what needs attention.
I am sure there are multiple angles which could solve for this, and anything that reduces email noise (especially with internal communication) and allows for quicker and more intuitive group management at the end user level has my vote. Maybe it is as simple as changing "Favorites" to "Following" and eliminating any Channels which are not followed from the user's view to reduce visual overload.
Hopefully my ramblings make some level of sense.
07-29-2019 02:53 AM
07-29-2019 02:54 AM
07-29-2019 02:54 AM - edited 07-29-2019 02:56 AM
It has been marked as Q4 CY19 on the Microsoft 365 Roadmap
However, we have all had notification that it should be in August.
Hope that helps!
07-29-2019 03:04 AM
07-29-2019 03:30 AM
07-29-2019 10:29 AM
07-29-2019 10:43 AM
07-29-2019 10:44 AM
08-07-2019 06:20 AM