Great video. But I’m not sure having many channels is a good advice for people working in 1000+ companies. We are flooded with so many teams with so many channels that it is impossible to keep track of everything.
It is all about how teams are structured. I have worked with company with way more than 1000 people and if thought about strategically works well. IMO the last thing you want is many many Teams with just a general channel
I agree with Daniel. We have users who created teams for various small projects and all operate on general channels. It's flooded and ugly. I'm cleaning it up so that all accounting related projects are channels in the accounting team. Files are all together and nice. Creating a new team is strictly for cross department projects that require separate permissions only for us moving forward. Thanks for the video🎉
I will be working with clients as a solo business owner and plan to use Teams so it appears the best way to ensure privacy of communication is separate Teams instead of Channels for each client. I only plan to have 10-15 clients max at any time. If i create a Communications Site and share with the Teams (private), will they be able to see what other clients have also viewed the documents or site or is that hidden? I noticed when i create a Teams environment and set restricted accesses, many times, I also have to go separately to the SharePoint site and do the same. I use M365 Business standard (not premium). I created a test team where I do all testing before I launch with actual clients.
Hey Daniel great video Thanks, have a question when you create a new channel in Teams they appear in SharePoint as folders but when you create a new folder in SharePoint at the documents root level they don't seem to appear in Teams as channel or as anything else. any idea?
Thanks Daniel!
Great video. But I’m not sure having many channels is a good advice for people working in 1000+ companies. We are flooded with so many teams with so many channels that it is impossible to keep track of everything.
It is all about how teams are structured. I have worked with company with way more than 1000 people and if thought about strategically works well. IMO the last thing you want is many many Teams with just a general channel
I agree with Daniel. We have users who created teams for various small projects and all operate on general channels. It's flooded and ugly. I'm cleaning it up so that all accounting related projects are channels in the accounting team. Files are all together and nice. Creating a new team is strictly for cross department projects that require separate permissions only for us moving forward. Thanks for the video🎉
I will be working with clients as a solo business owner and plan to use Teams so it appears the best way to ensure privacy of communication is separate Teams instead of Channels for each client. I only plan to have 10-15 clients max at any time. If i create a Communications Site and share with the Teams (private), will they be able to see what other clients have also viewed the documents or site or is that hidden? I noticed when i create a Teams environment and set restricted accesses, many times, I also have to go separately to the SharePoint site and do the same. I use M365 Business standard (not premium). I created a test team where I do all testing before I launch with actual clients.
Every Team you create has its own SharePoint Site
Connect on LinkedIn and we can chat www.linkedin.com/in/danielando?
Hey Daniel great video Thanks, have a question when you create a new channel in Teams they appear in SharePoint as folders but when you create a new folder in SharePoint at the documents root level they don't seem to appear in Teams as channel or as anything else. any idea?
That is correct