SOLVED
Home

Microsoft Teams Channels Permissions

%3CLINGO-SUB%20id%3D%22lingo-sub-295353%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295353%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20day%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20we%20are%20expanding%20Microsoft%20Teams%20adoption%20across%20our%20customer%20base%20we%20noticed%20that%20channel%20based%20permissions%20are%20not%20available.%20Is%20this%20something%20that%20is%20being%20worked%20on%3F%20Has%20anyone%20found%20a%20work%20around%20for%20this%3F%20We%20are%20finding%20it%20difficult%20to%20replicate%20the%20permissions%20that%20already%20exist%20in%20built%20out%20SharePoint%20sites%20with%20our%20clients.%20Anyone%20have%20suggestions%20on%20this%2C%20specifically%20how%20to%20deal%20with%20clients%20that%20have%20already%20been%20using%20SharePoint%3F%20Any%20feedback%20would%20be%20appreciated!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnthony%20Joseph%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-295353%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20Permissions%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295490%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295490%22%20slang%3D%22en-US%22%3EHello%20Anthony%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20see%20your%20problem%2C%20Especially%20if%20you%20have%20inherited%20permission%20hierarchy%20in%20SP%20project%20site%20and%20there%20is%20noway%20you%20would%20be%20able%20to%20accommodate%20these%20in%20Teams.%20though%20the%20channels%20permissions%20may%20address%20this%20for%20some%20extend%20but%20not%20all.%20We%20are%20already%20modifying%20for%20some%20of%20the%20project%20space%20in%20SharePoint%20to%20address%20this%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EThuyavan%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295376%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295376%22%20slang%3D%22en-US%22%3ENeed%20to%20look%20at%20breaking%20out%20projects%20into%20Teams%20instead%20of%20channels%2C%20most%20projects%20are%20going%20to%20need%20more%20then%20just%20a%20single%20folder%20for%20conversations%20etc.%20Then%20you%20will%20have%20permissions%20per%20project.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20it's%20just%20files%20your%20worried%20about%20you%20can%20still%20go%20to%20the%20%22Open%20in%20SharePoint%22%20link%20on%20the%20files%20tab%20and%20control%20permissions%20on%20the%20folders%20on%20the%20attached%20SharePoint%20site.%20Owners%20however%20will%20have%20permissions%20to%20all%20files%20regardless%20when%20it%20comes%20to%20group%20connected%20Teams%2FSharePoint%20sites%2C%20even%20after%20private%20channels%20drop.%3CBR%20%2F%3E%3CBR%20%2F%3ENot%20sure%20the%20feasibility%20but%20all%20projects%20I%20used%20to%20have%20in%20Teams%20would%20be%20per%20group%20of%20people.%20So%20usually%20each%20project%20has%20different%20Teams%20so%20they%20would%20be%20a%20Team%20for%20each.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295372%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295372%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20a%20problem.%20So%20for%20clients%20that%20have%20had%20existing%20SharePoint%20sites%20with%20elaborate%20permissions%2C%20we%20are%20finding%20it%20hard%20to%20mirror%20these%20permissions%20in%20Teams.%20For%20example%2C%20someone%20is%20in%20a%20Projects%20Team%20but%20should%20only%20have%20access%20to%20certain%20projects.%20In%20Teams%2C%20the%20different%20projects%20would%20be%20%22channels%22.%20In%20SharePoint%2C%20there%20are%20different%20document%20folders%20under%20the%20site%2C%20but%20users%20will%20not%20have%20permissions%20to%20each%20one.%20We%20are%20stumbling%20on%20problems%20once%20users%20are%20added%20to%20certain%20Teams%20and%20then%20have%20access%20to%20all%20the%20channels%20subsequently%20under%20these%20%22Teams%22.%20Does%20that%20make%20sense%3F%20Sorry%2C%20I%20am%20still%20trying%20to%20figure%20out%20this%20for%20myself%20as%20well.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295363%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295363%22%20slang%3D%22en-US%22%3EThis%20is%20being%20worked%20on%2C%20but%20I%20don%E2%80%99t%20know%20how%20far%20they%E2%80%99ve%20come%20with%20it!%3CBR%20%2F%3EIt%E2%80%99s%20possibe%20to%20change%20permissions%20in%20sharepoint%20but%20I%20don%E2%80%99t%20recommend%20it%20due%20to%20it%20can%20get%20complicated%20and%20inuative%20and%20it%20also%20only%20applies%20to%20files%2C%20not%20conversations%20etc..%3CBR%20%2F%3EEither%20create%20a%20new%20team%20or%20use%20a%20group%20chat%20in%20teams%20for%20people%20to%20have%20private%20conversations..chat%20also%20have%20a%20files%20tab%20and%20ability%20to%20add%20more%20tabs..%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295361%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295361%22%20slang%3D%22en-US%22%3EYes%2C%20on%20they%20are%20working%20on%20Teams%20private%20channels.%20Can%20you%20elaborate%20more%20on%20the%20SharePoint%20question%2C%20not%20quiet%20sure%20what%20your%20asking.%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665866%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665866%22%20slang%3D%22en-US%22%3EAs%20mentioned%20in%20above%20threads%2C%20we%20cannot%20have%20channel%20based%20permissions.%20Also%2C%20as%20we%20know%20all%20the%20channel%20will%20have%20same%20SharePoint%20site%20in%20common.%20Alternatively%2C%20we%20can%20split%20SharePoint%20and%20add%20as%20a%20link%20to%20tabs.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-684711%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-684711%22%20slang%3D%22en-US%22%3E%3CP%3EPermissions%20granularity%20is%20your%20decision%20point%3A%20Teams%20is%20currently%20very%20engagement%20based%2C%20not%20control%20based.%20Effectively%20everyone%20on%20the%20team%20must%20be%20trusted%20to%20competently%20and%20responsibly%20work%20with%20the%20information%20in%20the%20Team%20and%20in%20the%20channel.%20If%20that%20runs%20afoul%20of%20your%20intentions%2C%20then%20narrow%20the%20focus%20of%20the%20team%20and%20put%20your%20work%20product%20in%20SharePoint%20where%20you%20can%20control%20access%20and%20visibility%20with%20the%20granularity%20required.%20I%20miss%20the%20%22Visitor%22%20read-only%20concept%3A%20letting%20a%20set%20of%20users%20look%20but%20not%20touch%20is%20extremely%20helpful%2C%20but%20not%20currently%20available%20in%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-684838%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Channels%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-684838%22%20slang%3D%22en-US%22%3EYou%20totally%20have%20the%20same%20thing%20in%20Teams%20when%20it%20comes%20to%20files%2C%20just%20not%20conversations.%20I%20just%20wouldn't%20recommend%20it%20cause%20it%20adds%20complexity%20%3AP.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Good day, 

 

As we are expanding Microsoft Teams adoption across our customer base we noticed that channel based permissions are not available. Is this something that is being worked on? Has anyone found a work around for this? We are finding it difficult to replicate the permissions that already exist in built out SharePoint sites with our clients. Anyone have suggestions on this, specifically how to deal with clients that have already been using SharePoint? Any feedback would be appreciated!

 

Cheers,

 

Anthony Joseph

8 Replies
Highlighted
Yes, on they are working on Teams private channels. Can you elaborate more on the SharePoint question, not quiet sure what your asking. Thanks.
Highlighted
This is being worked on, but I don’t know how far they’ve come with it!
It’s possibe to change permissions in sharepoint but I don’t recommend it due to it can get complicated and inuative and it also only applies to files, not conversations etc..
Either create a new team or use a group chat in teams for people to have private conversations..chat also have a files tab and ability to add more tabs..

Adam
Highlighted

Not a problem. So for clients that have had existing SharePoint sites with elaborate permissions, we are finding it hard to mirror these permissions in Teams. For example, someone is in a Projects Team but should only have access to certain projects. In Teams, the different projects would be "channels". In SharePoint, there are different document folders under the site, but users will not have permissions to each one. We are stumbling on problems once users are added to certain Teams and then have access to all the channels subsequently under these "Teams". Does that make sense? Sorry, I am still trying to figure out this for myself as well. 

Highlighted
Need to look at breaking out projects into Teams instead of channels, most projects are going to need more then just a single folder for conversations etc. Then you will have permissions per project.

If it's just files your worried about you can still go to the "Open in SharePoint" link on the files tab and control permissions on the folders on the attached SharePoint site. Owners however will have permissions to all files regardless when it comes to group connected Teams/SharePoint sites, even after private channels drop.

Not sure the feasibility but all projects I used to have in Teams would be per group of people. So usually each project has different Teams so they would be a Team for each.
Highlighted
Solution
Hello Anthony,

I see your problem, Especially if you have inherited permission hierarchy in SP project site and there is noway you would be able to accommodate these in Teams. though the channels permissions may address this for some extend but not all. We are already modifying for some of the project space in SharePoint to address this issue.

Thanks,
Thuyavan
Highlighted
As mentioned in above threads, we cannot have channel based permissions. Also, as we know all the channel will have same SharePoint site in common. Alternatively, we can split SharePoint and add as a link to tabs.
Highlighted

Permissions granularity is your decision point: Teams is currently very engagement based, not control based. Effectively everyone on the team must be trusted to competently and responsibly work with the information in the Team and in the channel. If that runs afoul of your intentions, then narrow the focus of the team and put your work product in SharePoint where you can control access and visibility with the granularity required. I miss the "Visitor" read-only concept: letting a set of users look but not touch is extremely helpful, but not currently available in Teams.

Highlighted
You totally have the same thing in Teams when it comes to files, just not conversations. I just wouldn't recommend it cause it adds complexity :P.