08-09-2018 09:29 AM
08-09-2018 09:29 AM
Any updates soon to this page? https://support.office.com/en-us/article/create-a-private-channel-in-teams-60ef929a-4d68-418b-bf4f-5...
08-09-2018 09:36 AM
08-09-2018 09:43 AM
08-09-2018 09:45 AM
Thanks for raising this. We get the priority of private channels are are working on it - no further updates at this point.
10-19-2018 08:18 AM
I have so many uses for this feature. It would make Teams just about perfect. It would also help eliminate having to create so many individual Teams.
Example: I want to send faculty surveys to all my Program Directors. I have to create separate Teams for each Program. If I could have Private Channels, I could have one Team for Faculty Survey Distribution. Then, I could communicate to the Program Directors at the same time through the combined team, but could give them their Program surveys and private information through the Private Program channels.
Drill down a step further. The Program Director wants to give his faculty their surveys in Teams. They could then have a Program Team with separate channels for each faculty member. It would be easy to move files from their main channel to the individual faculty member's private channels.
Just one use of this feature that would be amazing!
12-06-2018 04:54 AM
12-06-2018 08:20 AM
@Duane Alleman wrote:
I wonder if the delay is on how they will handle the back end storage in SharePoint. Today a SP Site is created and a single document library is used for all files in that Teams area. Channels have separate folders for each channel in the single document library.
The MS Teams and SPO story is still in the early chapters, i guess.
On SharePoint you have the option of sharing specific documents and folders to specific people. You can give them edit and view only permissions. I don't understand why that capability can't be transferred to Teams. It seems like SharePoint has that functioning already.
12-06-2018 08:39 AMSolution
01-24-2019 01:54 PM
02-14-2019 06:31 AM
hahaha, every body have heard about this MAJOR HIGHEST VERY IMPORTANT feature for MS but we won't never see something...
03-14-2019 04:41 AM
06-18-2019 03:03 PM
I'm working on a Teams implementation for my company. We are a service company and work for various clients on various projects.
Currently, I am setting up each client as a Team with each project as a channel. This is working well for our company. I was really hoping private channels would be an option, so I can include contacts at each client in the "general" channel, but not give them access to our project channels.
Any recommendations for a workaround to achieve this? thanks
06-19-2019 06:08 AM
Per Adam's reply to your question, there's not anything you can do except to create a separate team. My question to you is if the client or you care about having all team members with access to project channels. In other words, is there something about your client's projects that requires not everyone at the team membership level have access? If it varies by project, then set up channels for those where it's okay all have access and teams for those where the client does not want everyone on their end to view/participate. That's what we've done. It's a clunky since with the former I have to remember to use @+name in conversations versus being able to use @+channel name.