Forum Discussion
RahamimL
Mar 10, 2019Iron Contributor
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...
- Mar 10, 2019Don'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.
RahamimL
Mar 10, 2019Iron Contributor
Are you suggesting we use the web browser instead of the file explorer? This means using 2 different platforms for working with files. Web browser for SharePoint and file explorer for OneDrive and personal files.
Mar 10, 2019
it doesn’t have to be all web. If you make use of office clients when you open items they all show up in recent lists. Also you have access to all your SharePoint locations from within the clients. Also on the web. You can get to them many ways and search from office portal home etc.
Anyway just trying to say I stay away from sync or network shares via explorer or anything resembling old school work habits at all costs.
Anyway just trying to say I stay away from sync or network shares via explorer or anything resembling old school work habits at all costs.
- Norman YoungMar 10, 2019MVP
Hello RahamimL,
I agree with ChrisWebbTech. Adopting modern work habits for modern tools is more desirable than maintaining the old school approach to document management.
SharePoint Maven has an excellent blog post - Solve all your SharePoint sync issues by using the new OneDrive Sync Client - that is worth reviewing and confirming settings in your tenant.
I hope this helps.
Norm
- RahamimLMar 10, 2019Iron Contributor
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.
- Mar 10, 2019Don'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.