Channel associated with a SharePoint library

%3CLINGO-SUB%20id%3D%22lingo-sub-300381%22%20slang%3D%22en-US%22%3EChannel%20associated%20with%20a%20SharePoint%20library%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300381%22%20slang%3D%22en-US%22%3E%3CP%3EI'd%20like%20to%20understand%20why%20Microsoft%20Teams%20made%20the%20choice%20to%20associate%20each%20channel%20with%20a%20folder%2C%20rather%20than%20associate%20it%20with%20a%20SharePoint%20library.%3C%2FP%3E%3CP%3EThe%20Information%20Architecture%20in%20SharePoint%20is%20site%20%26gt%3B%20library%20%26gt%3B%20folder.%20One%20MS%20Team%20%3D%20one%20SharePoint%20site%2C%20so%20moving%20to%20the%20next%20level%20I%20would%20have%20expected%20one%20channel%20%3D%20one%20library.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-300381%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChannels%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EInformation%20Architecture%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300980%22%20slang%3D%22en-US%22%3ERe%3A%20Channel%20associated%20with%20a%20SharePoint%20library%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300980%22%20slang%3D%22en-US%22%3ESorry%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300945%22%20slang%3D%22en-US%22%3ERe%3A%20Channel%20associated%20with%20a%20SharePoint%20library%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300945%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20as%20Chris%20said%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%26nbsp%3Bhoping%20that%20when%20I%20hear%20about%20the%20logic%20it'll%20make%20more%20sense%20and%20it'll%20tell%20me%20if%20there%20are%20opportunities%20to%20have%20it%20another%20way%20in%20the%20future.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300869%22%20slang%3D%22en-US%22%3ERe%3A%20Channel%20associated%20with%20a%20SharePoint%20library%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300869%22%20slang%3D%22en-US%22%3EYeah%20I%20think%20it%20was%20his%20%3A)%2C%20I%20think%20he%20just%20wanted%20to%20hear%20from%20Microsoft%20PM%20on%20this!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300866%22%20slang%3D%22en-US%22%3ERe%3A%20Channel%20associated%20with%20a%20SharePoint%20library%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300866%22%20slang%3D%22en-US%22%3ETher%20are%20a%20few%20long%20discussions%20on%20this%20topic%20in%20the%20teams%20forum!%20Search%20and%20you%20will%20find%20conversations%20about%20this%3C%2FLINGO-BODY%3E
Frequent Contributor

I'd like to understand why Microsoft Teams made the choice to associate each channel with a folder, rather than associate it with a SharePoint library.

The Information Architecture in SharePoint is site > library > folder. One MS Team = one SharePoint site, so moving to the next level I would have expected one channel = one library.

4 Replies
Ther are a few long discussions on this topic in the teams forum! Search and you will find conversations about this
Yeah I think it was his :), I think he just wanted to hear from Microsoft PM on this!

Just as Chris said :)

 

I am hoping that when I hear about the logic it'll make more sense and it'll tell me if there are opportunities to have it another way in the future.