Jan 17 2019 11:11 AM
Jan 17 2019 11:11 AM
Hello everyone and thanks in advance for the help!
Is there a way to share only one channel under a particular team and not all at once with the link?
We have a "Projects Awarded" and "Projects Bid" teams with many jobs/projects under each team.
I want to share just one of those individual channels or jobs to a particular person without them seeing all of the other projects. Is there a way to do that? I do I need to make a separate Team for every project?
Jan 17 2019 11:17 AMSolution
Jan 17 2019 11:33 AM
Jan 17 2019 12:44 PM
We create Teams per client with channels per project, that way if we join a project we can see what's happened before at that client. It works really well.
I wouldn't wait for a new feature that's not been announced or has any timescale set, while it's a common ask it's not always really the best solution.
Jan 17 2019 12:49 PM
Jan 17 2019 01:01 PM
Jan 17 2019 04:44 PM
May 22 2019 11:16 PM
@adam deltinger I don't think it's actually overated Adam. Take for a example, I have so many clients in my company and scartered around the globe.
Company A has many offices/sites in different parts of the country and similarly in different countries. I have many of these sites who do not want share projects they're working on until it's completed. Others are happy to share which is fine. Without the option to restrict users to channels, one is left with creating multiple teams for all the various sites within a single company.
So in my thoughts, 1 Teams is better, have multiple channels for the different sites then make them public or private to limit audience.
In my case I can potentially have 1 Team (1 Organisation) with 8 channels (8 sites) but currently at it stands, I have to create 8 separate teams for a single organization. No amount of proper planning will help in this case - the problem is it soon becomes a clutter.
May 22 2019 11:21 PM
May 22 2019 11:31 PM
I concur on that basis @adam deltinger, something gotta give somewhere. I've seen some really poorly implemented active directory, and other tree-node structure so - so I share the concerns where proper planning doesn't happen.
May 23 2019 01:59 AM
Jul 08 2019 02:08 AM
Jul 26 2019 12:29 PM
@adam deltinger I wrote an article last year about how you can make private folders within a Team.
I recently figured out how to do the opposite: invite Guests to individual folders/channels without giving them access to anything else in the Team. They won't have access to the conversations either.
Oct 29 2019 12:22 PM - edited Oct 29 2019 04:13 PM
@adam deltinger Holy crap this is limiting. We have a team that has multiple projects, and those projects will naturally have a different set of people working on it. We also may want to have management discussions that the rest of the members are either not privvy to or needed on. Having channels be a free-for-all (especially with the "private" designation when literally anyone can just waltz on in there) is a ridiculous stretch of reasonable user assumptions when trying to migrate to this tool from something like Slack. Why can't we just create a channel and add 2-3 people to it? Why was this not assumed to be the default use case/behavior/need for a product like teams?
Oct 29 2019 02:57 PM
Hopefully November. It was due in September and then October 2019 but now that window has nearly passed too.
Feb 06 2020 02:20 AM
@Mike_CotterI can currently do that, tagging the Channel security level as "private".
Channel access (and left pane display) is then limited to members that are added to the "Private Channel".
=> Problem is that you cannot create more than 30 "private" channels within the 200 allowed per TEAM.