SOLVED
Home

The same channel is serveral teams

%3CLINGO-SUB%20id%3D%22lingo-sub-803997%22%20slang%3D%22en-US%22%3ERe%3A%20The%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803997%22%20slang%3D%22en-US%22%3EA%20channel%20only%20exists%20in%20a%20single%20Team%2C%20and%20cannot%20be%20be%20connected%20%2F%20synced%20to%20another%20Team%20as%20such.%3CBR%20%2F%3E%3CBR%20%2F%3EAre%20you%20interested%20in%20the%20conversations%20in%20that%20channel%2C%20or%20the%20files%3F%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20it's%20the%20files%2C%20you%20could%20configure%20the%20permissions%20on%20the%20SharePoint%20folder%20for%20that%20channel%20as%20required%2C%20then%20add%20that%20library%20%2F%20folder%20as%20a%20tab%20in%20other%20Teams.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20it%20is%20more%20about%20the%20conversations%2C%20you%20would%20need%20to%20perhaps%20have%20a%20separate%20Team%2C%20which%20all%20the%20relevant%20users%20are%20members%20of%2C%20and%20use%20a%20channel%20in%20that%20Team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-804002%22%20slang%3D%22en-US%22%3ERe%3A%20The%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804002%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F392030%22%20target%3D%22_blank%22%3E%40Martin380%3C%2FA%3E%26nbsp%3BThere%20is%20also%20a%20new%20%22Cross%20channel%20posting%22%20function%20coming%20later.%20Currently%20listed%20for%20release%20in%20September%20(postponed%20from%20July).%20With%20this%20feature%20you%20will%20be%20able%20to%20post%20to%20multiple%20channels%20within%20the%20same%20team%20or%20in%20channels%20in%20different%20teams.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D52393%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D52393%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803979%22%20slang%3D%22en-US%22%3EThe%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803979%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20We%20are%20new%20to%20Teams%20and%20are%20just%20now%20creating%20our%20%22Teams%20Organisation%22.%20We%20see%20the%20need%20to%20connect%20(or%20sync)%20a%20channel%20into%20several%20different%20teams.%20Is%20this%20possible%2C%20or%20is%20there%20another%20way%20to%20see%20%22channel-information%22%20without%20having%20to%20look%20for%20it%20in%20several%20teams.%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-803979%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-804036%22%20slang%3D%22en-US%22%3ERe%3A%20The%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804036%22%20slang%3D%22en-US%22%3Eand%20in%20the%20meantime%2C%20you%20could%20sort%20of%20fake%20that%20functionality%2C%20by%20getting%20the%20email%20address%20for%20the%20relevant%20channel%20in%20each%20Team%20-%20then%20sending%20an%20email%20to%20all%20of%20those%20email%20addresses%20-%20which%20is%20effectively%20the%20same%20as%20cross%20posting%20(but%20does%20involve%20email%2C%20so%20not%20ideal).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-804164%22%20slang%3D%22en-US%22%3ERe%3A%20The%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804164%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506%22%20target%3D%22_blank%22%3E%40Rob%20Ellis%3C%2FA%3E%26nbsp%3BThanks%2C%20interesting%20with%20cross%20posting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20use%20external%20members%2C%20outside%20our%20organisation.%20As%20I%20understand%20it%2C%20all%20members%20are%20in%20the%20%22teams-level%22%20and%20not%20in%20the%20%22channel-level%22.%20We%20will%20use%20Teams%20for%20our%20product%20developments%20and%20the%20idea%20was%2Fis%20to%20form%20different%20teams%20for%20different%20developments%20tasks%3A%20electronics%2C%20mechanics%2C%20marketing%2C%20sales%2C%20purchasing%20etc.%20Sometimes%2C%20espacially%20for%20external%20members%2C%20there%20can%20be%20confidentiality%20issues.%20It%20would%20be%20great%20if%20it%20was%20possible%20to%20invite%20certain%20members%20to%20a%20specific%20channel%20instead%20of%20%22the%20hole%20team%22.%20This%20way%2C%20the%20team%20could%20have%20general%20discussions%20without%20revealing%20secrets%20to%20the%20%22only-channel-members%22.%3C%2FP%3E%3CP%3EHow%20do%20other%20organisations%20deal%20with%20this%3F%20It%20feels%20like%20this%20issue%20would%20not%20be%20unique%20for%20us...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-804169%22%20slang%3D%22en-US%22%3ERe%3A%20The%20same%20channel%20is%20serveral%20teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804169%22%20slang%3D%22en-US%22%3ECurrently%20you%20would%20be%20best%20to%20create%20additional%20Teams%2C%20and%20have%20your%20guests%20as%20members%20in%20those%20(although%20I%20appreciate%20that%20comes%20with%20an%20overhead%20due%20to%20potentially%20doubling%20up%20on%20the%20number%20of%20Teams).%3CBR%20%2F%3E%3CBR%20%2F%3ERolling%20out%20from%20September%20will%20be%20'private%20channels'%20-%20where%20you%20can%20lock%20down%20a%20channel%20to%20a%20subset%20of%20the%20Team%20members%20-%20so%20that%20will%20be%20worth%20considering.%3C%2FLINGO-BODY%3E
Martin380
New Contributor

Hi. We are new to Teams and are just now creating our "Teams Organisation". We see the need to connect (or sync) a channel into several different teams. Is this possible, or is there another way to see "channel-information" without having to look for it in several teams. 

Thanks,

Martin

5 Replies
Solution
A channel only exists in a single Team, and cannot be be connected / synced to another Team as such.

Are you interested in the conversations in that channel, or the files?

If it's the files, you could configure the permissions on the SharePoint folder for that channel as required, then add that library / folder as a tab in other Teams.

If it is more about the conversations, you would need to perhaps have a separate Team, which all the relevant users are members of, and use a channel in that Team.

@Martin380 There is also a new "Cross channel posting" function coming later. Currently listed for release in September (postponed from July). With this feature you will be able to post to multiple channels within the same team or in channels in different teams.

https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=52393

and in the meantime, you could sort of fake that functionality, by getting the email address for the relevant channel in each Team - then sending an email to all of those email addresses - which is effectively the same as cross posting (but does involve email, so not ideal).

@Rob Ellis Thanks, interesting with cross posting.

 

We also use external members, outside our organisation. As I understand it, all members are in the "teams-level" and not in the "channel-level". We will use Teams for our product developments and the idea was/is to form different teams for different developments tasks: electronics, mechanics, marketing, sales, purchasing etc. Sometimes, espacially for external members, there can be confidentiality issues. It would be great if it was possible to invite certain members to a specific channel instead of "the hole team". This way, the team could have general discussions without revealing secrets to the "only-channel-members".

How do other organisations deal with this? It feels like this issue would not be unique for us...

Currently you would be best to create additional Teams, and have your guests as members in those (although I appreciate that comes with an overhead due to potentially doubling up on the number of Teams).

Rolling out from September will be 'private channels' - where you can lock down a channel to a subset of the Team members - so that will be worth considering.