SOLVED

Private Channel Update

%3CLINGO-SUB%20id%3D%22lingo-sub-226289%22%20slang%3D%22en-US%22%3EPrivate%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226289%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20ability%20to%20create%20private%20channels%20is%20important%20to%20my%20company.%20I%20know%20this%20is%20in%20active%20development.%20What%20stage%20is%20this%20in%20now%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20still%20in%20early%20development%3F%20Has%20it%20made%20it%20to%20inside%20rings%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-226289%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConversations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308954%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308954%22%20slang%3D%22en-US%22%3EThe%20only%20thing%20we%20hear%20from%20MS%20is%20%22we're%20working%20on%20it%22.%20I%20am%20seriously%20disappointed%20by%20the%20lack%20of%20info%20we%20have!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300137%22%20slang%3D%22en-US%22%3ERE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300137%22%20slang%3D%22en-US%22%3EThe%20lack%20of%20channel-level%20security%20is%20the%20number%20one%20barrier%20to%20a%20widespread%20rollout%20for%20our%20firm.%20This%20has%20been%20%22in%20the%20works%22%20for%20nearly%20two%20years%20with%20a%20%22coming%20soon%22%20promise.%20If%20this%20is%20not%20resolved%20%22soon%22%20(which%20I%20am%20defining%20as%20%22the%20next%20quarter%22)%2C%20I%20suspect%20our%20adoption%20rate%20will%20tank.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300123%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300123%22%20slang%3D%22en-US%22%3EYes%3B%20a%20consulting%20vendor%20and%20all%20of%20our%20clients%20need%20private%20channels%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300084%22%20slang%3D%22en-US%22%3ERE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300084%22%20slang%3D%22en-US%22%3EDesperately%20need%20channel%20privacy%20-%20and%20including%20the%20ability%20to%20invite%20guests%20only%20to%20a%20channel%20as%20opposed%20to%20visibility%20to%20the%20entire%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299987%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299987%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%20we've%20heard%20so%20many%20times%20%22we're%20working%20on%20it%22.%20Could%20you%20please%20give%20at%20least%20an%20approximate%20ETA%3F%20It's%20been%202%20years%20since%20we%20asked%20for%20this!%20This%20is%20the%20number%20one%20topic%20on%20Teams!%20Please%20help%20us%20going%20one%20step%20further%20into%20the%20collaborative%20work%20mode!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227106%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227106%22%20slang%3D%22en-US%22%3EI%20agree%20to%20some%20degree%2C%20but%20I%20think%20ti's%20going%20to%20cause%20more%20headache's%20for%20support%20as%20well.%20Going%20to%20have%20so%20many%20users%20trying%20to%20link%20messages%2C%20%40mention%20people%20from%20inside%20private%20channels%20and%20whatever%20else%20that%20will%20just%20cause%20confusion%20to%20normal%20users.%20It'll%20fix%20some%20things%20for%20power%20users%20but%20I%20can%20also%20see%20it%20being%20an%20issue%20as%20well%20for%20the%20typical%20'user'%20lol.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227104%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227104%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20so.%20This%20would%20make%20adoption%20SO%20much%20easier%20and%20really%20reduce%20the%20number%20of%20required%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227102%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227102%22%20slang%3D%22en-US%22%3EI%20would%20set%20your%20expectations%20for%20something%20at%20ignite.%20Which%20is%20a%20month%20and%20half%20away%2C%20I'd%20be%20surprised%20if%20they%20don't%20discuss%20it%20or%20have%20something%20ready%20by%20then.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227087%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227087%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20share%20any%20update%20besides%20'stay%20tuned'%3F%20We've%20been%20staying%20tuned%20for%20quite%20a%20while%20on%20this%20request.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226873%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226873%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153758%22%20target%3D%22_blank%22%3E%40Mark%20Paradis%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EI%20am%20not%20sure%20if%20this%20is%20the%20same%20use%20case.%20But%20we%20desperately%20need%20the%20ability%20to%20share%201%20single%20channel%20amongst%20multiple%20teams%20to%20create%20a%20cross%20communication%20with%20different%20teams.%20Use%20Case%20is%3A%20Sales%20Team%2C%20X%20Product%20Team%20need%20one%20channel%20shared%20in%20both%20teams%20to%20communicate%20about%20one%20single%20product%20but%20no%20share%20EVERY%20other%20channel%20with%20them.%20Also%20we%20don't%20want%20to%20create%20a%20whole%20other%20team%20that%20combines%20EVERYONE%20from%20both%20teams%20creating%20a%20proliferation%20of%20teams.%20Is%20that%20what%20this%20is%20kinda%20referring%20to%3F%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EFor%20this%20example%2C%20we%20usually%20create%20a%20separate%20Team%20and%20that%20has%20members%20from%20both%20Teams%20so%20that%20they%20can%20communicate%20and%20work%20together.%26nbsp%3B%20This%20seems%20to%20work%20well%20for%20us.%26nbsp%3B%20But%2C%20we%20definitely%20need%20private%20channels%20so%20that%20some%20content%2Fchat%20can%20be%20limited%20to%20specific%20people.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226794%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226794%22%20slang%3D%22en-US%22%3ENow%20that%20the%20Skype%20Roadmap%20is%20almost%20completed%2C%20I%20expect%20to%20see%20more%20focus%20on%20expanding%20Teams%20now%20than%20we%20have%20over%20the%20past%20year.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226420%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226420%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20probably%20our%20most%20requested%20item.%26nbsp%3B%20Nobody%20internally%20cares%20about%20the%20'bot'%26nbsp%3Bsupport%20that%20has%20been%20recently%20announced%2C%20they%20are%20looking%20for%20real%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226402%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226402%22%20slang%3D%22en-US%22%3ECan%20you%20send%20a%20link%20to%20the%20specific%20User%20Voice%20item%20so%20I%20can%20vote%3F%20thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226377%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226377%22%20slang%3D%22en-US%22%3EThank%20you%2C%20Roshin.%20Is%20there%20any%20more%20information%20available%3F%20Is%20this%20likely%20to%20be%20released%20%22soon%22%20or%20is%20it%20a%20larger%20change%20that%20is%20likely%20to%20take%20several%20months%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226358%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226358%22%20slang%3D%22en-US%22%3EThis%20is%20different.%20This%20is%20a%20channel%20that%20has%20a%20different%20set%20of%20members%20than%20the%20team%20it's%20in.%20for%20example%3A%20a%20Management%20channel%20in%20a%20department%20team%20should%20have%20restricted%20access.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226353%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226353%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mark%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESharing%20a%20single%20channel%20between%20two%26nbsp%3Bteams%20is%20a%20different%20scenario%20from%20private%20channels.%20We%20are%20aware%20of%20this%20requirement%20and%20have%20it%20in%20our%20backlog.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20upvote%20this%20requirement%20in%20the%20Microsoft%20Teams%20UserVoice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226352%22%20slang%3D%22en-US%22%3ERE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226352%22%20slang%3D%22en-US%22%3ESame%20here.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226344%22%20slang%3D%22en-US%22%3ERe%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226344%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Steven%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPrivate%20channels%20is%20definitely%20a%20high%20priority%20for%20us%20-%20we%20are%20working%20on%20it.%20Stay%26nbsp%3Btuned%20for%20more%20updates%20coming%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226320%22%20slang%3D%22en-US%22%3ERE%3A%20Private%20Channel%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226320%22%20slang%3D%22en-US%22%3EI%20am%20not%20sure%20if%20this%20is%20the%20same%20use%20case.%20But%20we%20desperately%20need%20the%20ability%20to%20share%201%20single%20channel%20amongst%20multiple%20teams%20to%20create%20a%20cross%20communication%20with%20different%20teams.%20Use%20Case%20is%3A%20Sales%20Team%2C%20X%20Product%20Team%20need%20one%20channel%20shared%20in%20both%20teams%20to%20communicate%20about%20one%20single%20product%20but%20no%20share%20EVERY%20other%20channel%20with%20them.%20Also%20we%20don't%20want%20to%20create%20a%20whole%20other%20team%20that%20combines%20EVERYONE%20from%20both%20teams%20creating%20a%20proliferation%20of%20teams.%20Is%20that%20what%20this%20is%20kinda%20referring%20to%3F%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

The ability to create private channels is important to my company. I know this is in active development. What stage is this in now?

 

Is it still in early development? Has it made it to inside rings?

19 Replies
Highlighted
I am not sure if this is the same use case. But we desperately need the ability to share 1 single channel amongst multiple teams to create a cross communication with different teams. Use Case is: Sales Team, X Product Team need one channel shared in both teams to communicate about one single product but no share EVERY other channel with them. Also we don't want to create a whole other team that combines EVERYONE from both teams creating a proliferation of teams. Is that what this is kinda referring to?
Highlighted

Hi Steven,

 

Private channels is definitely a high priority for us - we are working on it. Stay tuned for more updates coming on this.

Highlighted
Same here.
Highlighted
Best Response confirmed by Kevin Crossman (MVP)
Solution

Hi Mark,

 

Sharing a single channel between two teams is a different scenario from private channels. We are aware of this requirement and have it in our backlog.

 

Please upvote this requirement in the Microsoft Teams UserVoice.

Highlighted
This is different. This is a channel that has a different set of members than the team it's in. for example: a Management channel in a department team should have restricted access.
Highlighted
Thank you, Roshin. Is there any more information available? Is this likely to be released "soon" or is it a larger change that is likely to take several months?
Highlighted
Can you send a link to the specific User Voice item so I can vote? thanks!
Highlighted

This is probably our most requested item.  Nobody internally cares about the 'bot' support that has been recently announced, they are looking for real functionality.

Highlighted
Now that the Skype Roadmap is almost completed, I expect to see more focus on expanding Teams now than we have over the past year.
Highlighted

@Mark Paradis wrote:
I am not sure if this is the same use case. But we desperately need the ability to share 1 single channel amongst multiple teams to create a cross communication with different teams. Use Case is: Sales Team, X Product Team need one channel shared in both teams to communicate about one single product but no share EVERY other channel with them. Also we don't want to create a whole other team that combines EVERYONE from both teams creating a proliferation of teams. Is that what this is kinda referring to?

For this example, we usually create a separate Team and that has members from both Teams so that they can communicate and work together.  This seems to work well for us.  But, we definitely need private channels so that some content/chat can be limited to specific people.  

Highlighted

Can you share any update besides 'stay tuned'? We've been staying tuned for quite a while on this request.

Highlighted
I would set your expectations for something at ignite. Which is a month and half away, I'd be surprised if they don't discuss it or have something ready by then.
Highlighted

I hope so. This would make adoption SO much easier and really reduce the number of required Teams.

Highlighted
I agree to some degree, but I think ti's going to cause more headache's for support as well. Going to have so many users trying to link messages, @mention people from inside private channels and whatever else that will just cause confusion to normal users. It'll fix some things for power users but I can also see it being an issue as well for the typical 'user' lol.
Highlighted

Hey, we've heard so many times "we're working on it". Could you please give at least an approximate ETA? It's been 2 years since we asked for this! This is the number one topic on Teams! Please help us going one step further into the collaborative work mode!

Highlighted
Desperately need channel privacy - and including the ability to invite guests only to a channel as opposed to visibility to the entire team.
Highlighted
Yes; a consulting vendor and all of our clients need private channels
Highlighted
The lack of channel-level security is the number one barrier to a widespread rollout for our firm. This has been "in the works" for nearly two years with a "coming soon" promise. If this is not resolved "soon" (which I am defining as "the next quarter"), I suspect our adoption rate will tank.
Highlighted
The only thing we hear from MS is "we're working on it". I am seriously disappointed by the lack of info we have!