SOLVED

Identifying Team Channel associated with SharePoint folder

%3CLINGO-SUB%20id%3D%22lingo-sub-682119%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682119%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9832%22%20target%3D%22_blank%22%3E%40Wyn%20Hopkins%3C%2FA%3E%26nbsp%3BI%20have%20probably%20misunderstood%20your%20question%2C%20but%20the%20folder%20is%20called%20the%20name%20of%20the%20Channel%20and%20the%20SharePoint%20site%20is%20the%20name%20of%20the%20Team%20I%20believe.%26nbsp%3B%20In%20most%20places%20around%20sharepoint%2C%20you%20can%20see%20the%20file%20path%20of%20a%20document%2C%20therefore%20this%20will%20give%20you%20the%20Team%20and%20channel%20the%20document%20is%20in.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682134%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682134%22%20slang%3D%22en-US%22%3EHi%20Tanya%2C%3CBR%20%2F%3EThanks%20for%20getting%20back%20to%20me.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20know%20the%20Team%20exists%20then%20yes%20I%20can%20see%20that%20the%20names%20match%2C%20but%20from%20a%20purely%20SharePoint%20interface%20point%20of%20view%20is%20there%20a%20way%20of%20identifying%20that%20the%20folder%20is%20generated%20by%20%2F%20associated%20with%20a%20Team%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20if%20someone%20changes%20the%20Team%20name%20the%20associated%20SharePoint%20site%20name%20doesn't%20change%20making%20things%20even%20harder%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682211%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682211%22%20slang%3D%22en-US%22%3EThey%20were%20supposed%20to%20rollout%20a%20feature%20that%20marks%20teams%20channel%20folders%20with%20an%20icon%20on%20it%20indicating%20as%20such%20but%20haven%E2%80%99t%20seen%20it.%20I%20think%20it%20might%20release%20when%20they%20release%20the%20SharePoint%20files%20tab%20replacement.%20If%20not%20it%E2%80%99ll%20be%20at%20some%20point%20in%20the%20future.%20%3CBR%20%2F%3E%3CBR%20%2F%3EAnyway%20it%E2%80%99s%20coming.%20Just%20a%20matter%20of%20when.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682837%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682837%22%20slang%3D%22en-US%22%3EThanks%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-695214%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695214%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9832%22%20target%3D%22_blank%22%3E%40Wyn%20Hopkins%3C%2FA%3E%26nbsp%3B%20Just%20seen%20a%20message%20in%20our%20tenant%20this%20morning%20saying%20this%20feature%20is%20rolling%20out!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682112%22%20slang%3D%22en-US%22%3EIdentifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682112%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20you%20add%20files%20to%20a%20Team%20Channel%20they%20get%20added%20to%20SharePoint.%20However%2C%20once%20you're%20in%20SharePoint%20is%20there%20any%20way%20of%20seeing%20which%20Team%20%2F%20Channel%20that%20folder%20is%20associated%20with%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-682112%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-695219%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695219%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYeah%2C%20saw%20that%20too!%20Just%26nbsp%3B%20to%20bad%20renaming%20folders%20etc%20isn't%20reflected%20between%20the%20services%20yet%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789363%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789363%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2552%22%20target%3D%22_blank%22%3E%40Tanya%20Denton%3C%2FA%3E%26nbsp%3BDo%20you%20or%20does%20anyone%20here%20have%20this%20actually%20available%3F%20I%20got%20the%20message%20back%20in%20June%20as%20well%2C%20and%2045%2B%20days%20later%20I%20don't%20see%20this%20integration%20in%20either%20tenant%20I%20have%20admin%20access%20to.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789388%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789388%22%20slang%3D%22en-US%22%3ENope%20I%20haven%E2%80%99t.%20Pretty%20sure%20it%E2%80%99s%20tied%20to%20the%20Teams%20files%20tab%20update%20which%20seems%20to%20be%20inevitably%20pushed%20back%20but%20guess%20we%20will%20see%20it%20when%20we%20see%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-790478%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-790478%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BThanks.%20My%20concern%20is%20in%20order%20for%20%22Private%20Channels%22%20to%20work%2C%20which%20is%20now%20announced%20for%20September%20release%2C%20the%20SharePoint%20backend%20has%20to%20be%20very%20%22Teams%20Aware%22%20to%20properly%20handle%20the%20folder%20security%20for%20the%20Channel%20folders%20under%20%5CDocuments.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20they%20cannot%20even%20get%20the%20UI%20to%20show%20that%20SharePoint%20is%20Teams%20aware%2C%20not%20sure%20how%20the%20more%20complex%20Teams%20permissions%20will%20be%20maintained.%20I%20know%20MS%20can%20do%20it.%20I%20am%20very%20skeptical%20of%20the%20September%20date.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-790781%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-790781%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236847%22%20target%3D%22_blank%22%3E%40Ed%20Hansberry%3C%2FA%3E%26nbsp%3BNope%20not%20here%2C%20it%20is%20on%20my%20list%20of%20things%20to%20check%20each%20week%20-%20you%20know%20the%20changes%2Fnew%20features%20that%20appear%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1314614%22%20slang%3D%22en-US%22%3ERe%3A%20Identifying%20Team%20Channel%20associated%20with%20SharePoint%20folder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1314614%22%20slang%3D%22en-US%22%3EGlad%20this%20post%20exists%20-%20thanks%20%40Wyn!%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20amazed%20this%20doesn't%20exist%20already...%20a%20normal%20%22recursive%22%20way%20to%20see%20that%20the%20folder%20exists%20because%20of%20aTeam%20makes%20sense.%20If%20we%20already%20have%20a%20folder%20structure%20in%20SharePoint%20to%20meet%20our%20Taxonomy%20needs%2C%20these%20%22channel%20folders%22%20can%20just%20destroy%20that.%20If%20there%20were%20a%20way%20to%20identify%20it%20with%20a%20logo%2C%20and%20also%20a%20metadata%20field%20(a%20new%20column%20type%20of%20%22Channel%3F%22%20or%20simialr%20with%20Team%20and%20Not%20Team%20as%20Choices%20would%20be%20great!)%20this%20would%20save%20a%20lot%20of%20grief.%3CBR%20%2F%3E%3CBR%20%2F%3EDid%20you%20know.%2C..%20if%20you%20create%20a%20channel%20with%20the%20exact%20same%20name%20as%20an%20existing%20folder%2C%20it%20will%20connect%20that%20new%20channel%20to%20that%20existing%20folder.%3CBR%20%2F%3E%3CBR%20%2F%3EFinally...%20don't%20even%20get%20me%20started%20on%20%22Private%20Channels%20create%20a%20whole%20sub-site%22%20-%20that%20is%20MS%20really%20dropping%20the%20ball%20on%20that%20feature.%20It%20should%20create%20a%20secured%20folder%20in%20that%20same%20existing%20default%20library...%20not%20a%20new%20whole%20sub%20site%20for%20that%20Private%20channel!%20Good%20grief...%3C%2FLINGO-BODY%3E
MVP

When you add files to a Team Channel they get added to SharePoint. However, once you're in SharePoint is there any way of seeing which Team / Channel that folder is associated with?

11 Replies
Highlighted

@Wyn Hopkins I have probably misunderstood your question, but the folder is called the name of the Channel and the SharePoint site is the name of the Team I believe.  In most places around sharepoint, you can see the file path of a document, therefore this will give you the Team and channel the document is in.

Highlighted
Hi Tanya,
Thanks for getting back to me.

If I know the Team exists then yes I can see that the names match, but from a purely SharePoint interface point of view is there a way of identifying that the folder is generated by / associated with a Team?

Also, if someone changes the Team name the associated SharePoint site name doesn't change making things even harder
Highlighted
Best Response confirmed by Wyn Hopkins (MVP)
Solution
They were supposed to rollout a feature that marks teams channel folders with an icon on it indicating as such but haven’t seen it. I think it might release when they release the SharePoint files tab replacement. If not it’ll be at some point in the future.

Anyway it’s coming. Just a matter of when.
Highlighted
Highlighted

@Wyn Hopkins  Just seen a message in our tenant this morning saying this feature is rolling out!

Highlighted

@Tanya Denton 

 

Yeah, saw that too! Just  to bad renaming folders etc isn't reflected between the services yet

Highlighted

@Tanya Denton Do you or does anyone here have this actually available? I got the message back in June as well, and 45+ days later I don't see this integration in either tenant I have admin access to.

Highlighted
Nope I haven’t. Pretty sure it’s tied to the Teams files tab update which seems to be inevitably pushed back but guess we will see it when we see it.
Highlighted

@Chris Webb Thanks. My concern is in order for "Private Channels" to work, which is now announced for September release, the SharePoint backend has to be very "Teams Aware" to properly handle the folder security for the Channel folders under \Documents.

If they cannot even get the UI to show that SharePoint is Teams aware, not sure how the more complex Teams permissions will be maintained. I know MS can do it. I am very skeptical of the September date.

Highlighted

@Ed Hansberry Nope not here, it is on my list of things to check each week - you know the changes/new features that appear :)

Highlighted
Glad this post exists - thanks @Wyn!

I'm amazed this doesn't exist already... a normal "recursive" way to see that the folder exists because of aTeam makes sense. If we already have a folder structure in SharePoint to meet our Taxonomy needs, these "channel folders" can just destroy that. If there were a way to identify it with a logo, and also a metadata field (a new column type of "Channel?" or simialr with Team and Not Team as Choices would be great!) this would save a lot of grief.

Did you know.,.. if you create a channel with the exact same name as an existing folder, it will connect that new channel to that existing folder.

Finally... don't even get me started on "Private Channels create a whole sub-site" - that is MS really dropping the ball on that feature. It should create a secured folder in that same existing default library... not a new whole sub site for that Private channel! Good grief...