Hi everyone! We're in the process of deciding whether to adopt SharePoint as our company-wide file sharing system. However, we're torn between using SharePoint on its own or integrating it with Teams. From what I've gathered in my initial tests, SharePoint's file permissions can be implemented similarly regardless of whether it's standalone or paired with Teams. The main difference seems to be the added user-friendly access through a Teams channel.
Our main objectives are to ensure that each department has access only to their specific folder in a main 'shared' directory, while having a public folder open to everyone for shared files. I'm curious—what are the potential drawbacks of using the Teams integration for our file sharing?
1 Answer
It's important to remember that Teams actually uses SharePoint for file storage. So technically, you're still working with SharePoint either way. I’d recommend against setting up a 'main' SharePoint site with individual folders for each department. This can mirror your old setup, which is tempting but not ideal for SharePoint’s functionality and can lead to performance issues. Instead, consider creating a separate Microsoft 365 Group or Team for each department to manage their files. That would be a more efficient setup!
Are there really no differences in permissions between a standalone SharePoint site and a Teams-connected one? I keep hearing that it's better to create individual department sites rather than just following traditional file structures. What’s the reasoning behind that?