implementation
1 TopicRequesting best practice discussion on setting up Teams and Channels
Hello everyone! I'm interested in soliciting discussion on the best practices when setting up teams and channels inside of MS Teams. First, let me give you a bit of overview in our deployment. We are using Teams to manage most of our internal projects, and while it works great internally, our setup causes some problems when trying to bring people outside of our organisation into Teams for discussion and collaboration. As an example, we have set up a Production team with channels for each client. This works great internally. Each Production team member has access to the information they need to complete deployment for the client with all the rich features Teams brings to the table. The issue comes when we want to provide clients access to their project. Currently, unless we're missing something, outside users can only be added to teams, and not channels. To get around this, it seems like we'd need to change our Teams setup and create teams for each client, which seems excessive and really counter-productive from an efficiency standpoint. We would have hundreds of teams to manage, which seems like an administrative nightmare. The alternative to this is to create secondary teams for the client to join, but then we have the issue of either having two copies of documents (one in the Production team and a dupe in the client's team), and two different conversation threads, etc. Operationally, we're kinda stuck on this one and would be very appreciative of advice from anyone else running into similar issues. It seems like being able to share channels outside of the org would be the answer, but we're assuming there is some kind of technical hurdle with this since it's not already a 'feature'. Thank you all, and I look forward to your thoughts. ToddSolved2.4KViews1like8Comments
