Forum Discussion
Solved
Syncing SharePoint sites with OneDrive
Hi all, We're in the middle of migrating our network drives from our local storage to SharePoint Online. Our computers are windows 10 education with office 2016. We are about to change to windows 10...
- Don't focus on just the files part. Spin it as here is your Team in Microsoft Teams, if you have it, or SharePoint Team site, with news this and here are you're files, and this is how you can share them with other departments while maintaining privacy to just your department on the files etc.
This is just my opinion but I've always gone the approach depending on your org structure, is having a Public communication SharePoint site for Each departments News and "Global" file document libraries, where files that should be available to the org are, for instance, HR's comm site would have benefits documents etc. in them, where the whole org has access.
Then you have a Private Team site for each department where their own files are, if they need to share the file to just a few people as exceptions you have the Share button to use.
This is usually the approach I take, sense you usually have Global drivers with no security, and each department has a folder, and another "Private" drive where each department can only see / access their own folder, these get moved into Private Department / Team sites.
This leads more towards Team area's and less about just Files and folders.
But there is another wrench here, where if you have a repeatable type of document repository such as projects, or customers where documents are consistent across the board but separated by an entity you start to use a central single repository and use metadata, so that finding these files becomes much easier. But I'm kind of going off normal standard network driver migrations as most of the time, the use case is how I laid it out above.
I also agree with ChrisWebbTech. I just hope my manager would agree with me as well. It'll be hard to move someone from shared network drives to working on files from a web browser \ office apps and syncing only specific folders.
Don't focus on just the files part. Spin it as here is your Team in Microsoft Teams, if you have it, or SharePoint Team site, with news this and here are you're files, and this is how you can share them with other departments while maintaining privacy to just your department on the files etc.
This is just my opinion but I've always gone the approach depending on your org structure, is having a Public communication SharePoint site for Each departments News and "Global" file document libraries, where files that should be available to the org are, for instance, HR's comm site would have benefits documents etc. in them, where the whole org has access.
Then you have a Private Team site for each department where their own files are, if they need to share the file to just a few people as exceptions you have the Share button to use.
This is usually the approach I take, sense you usually have Global drivers with no security, and each department has a folder, and another "Private" drive where each department can only see / access their own folder, these get moved into Private Department / Team sites.
This leads more towards Team area's and less about just Files and folders.
But there is another wrench here, where if you have a repeatable type of document repository such as projects, or customers where documents are consistent across the board but separated by an entity you start to use a central single repository and use metadata, so that finding these files becomes much easier. But I'm kind of going off normal standard network driver migrations as most of the time, the use case is how I laid it out above.
This is just my opinion but I've always gone the approach depending on your org structure, is having a Public communication SharePoint site for Each departments News and "Global" file document libraries, where files that should be available to the org are, for instance, HR's comm site would have benefits documents etc. in them, where the whole org has access.
Then you have a Private Team site for each department where their own files are, if they need to share the file to just a few people as exceptions you have the Share button to use.
This is usually the approach I take, sense you usually have Global drivers with no security, and each department has a folder, and another "Private" drive where each department can only see / access their own folder, these get moved into Private Department / Team sites.
This leads more towards Team area's and less about just Files and folders.
But there is another wrench here, where if you have a repeatable type of document repository such as projects, or customers where documents are consistent across the board but separated by an entity you start to use a central single repository and use metadata, so that finding these files becomes much easier. But I'm kind of going off normal standard network driver migrations as most of the time, the use case is how I laid it out above.
I have to admit you convinced me with your first post.
If the way we want to use office 365 is with cross platforms devices (workstations \ mobile devices \ home computers), we need to make the user realize that the best way for him to work is: "How does it work on your mobile device". This means that since in your phone there is no file explorer to sync, they need to either download another app \ using the browser to get to the file they need to work on.
Also, like you said, there comes a time where the IT just stands on it's feet and says: "This is how you need to work and that's it!". We need to remember social media apps didn't come with any manuals. Yet, people swim in those apps like pros.
