Skip to main content

If you want multiple users to collaborate on the folders depending on their permissions/access level, why not use SharePoint site?

You can divide the structure between libraries instead of folders (they give you more options) and after navigating to the site, every user will get a security-trimmed view with only the elements he has access to, e.g:

User A:

User A: ||- Group FoldersGroup Folders
|- - -Financials (access by: UserA, UserB) 
|- - -Design (access by: User A, UserC). 
|- - -Etc.

|- User foldersUser folders
|- - -UserA 
|- - - - -Content

User B:

User B: ||- Group FoldersGroup Folders
|- - -Financials (access by: UserA, UserB) 
|- - -Etc.

|- User foldersUser folders
|- - -UserB 
|- - - - -Content

In this way a fresh user will always have access to company content and importantly - its updates and new additions.

You can achieve that by navigating to library/list/folder (depending on your choice) sharing settings (List>List Settings>Permissions; Library>Library Settings>Permissions; Folder>...>Shared With>Advanced) and breaking the permission inheritance. Have a look here: https://social.technet.microsoft.com/wiki/contents/articles/36004.restoring-and-removing-item-permissions-in-subfolders-for-sharepoint-online-using-powershell.aspx

Additionally, at a later stage you can set up a script that will be mapping the libraries to users' computers and synchronizing them so that they have local copies.

ODB is intended rather for personal use. If you expect your users to have all the same folder structure, you can use a Powershell script to implement it for every user.

If you want multiple users to collaborate on the folders depending on their permissions/access level, why not use SharePoint site?

You can divide the structure between libraries instead of folders (they give you more options) and after navigating to the site, every user will get a security-trimmed view with only the elements he has access to, e.g:

User A: |- Group Folders |- - -Financials (access by: UserA, UserB) |- - -Design (access by: User A, UserC). |- - -Etc.

|- User folders |- - -UserA |- - - - -Content

User B: |- Group Folders |- - -Financials (access by: UserA, UserB) |- - -Etc.

|- User folders |- - -UserB |- - - - -Content

In this way a fresh user will always have access to company content and importantly - its updates and new additions.

You can achieve that by navigating to library/list/folder (depending on your choice) sharing settings (List>List Settings>Permissions; Library>Library Settings>Permissions; Folder>...>Shared With>Advanced) and breaking the permission inheritance. Have a look here: https://social.technet.microsoft.com/wiki/contents/articles/36004.restoring-and-removing-item-permissions-in-subfolders-for-sharepoint-online-using-powershell.aspx

Additionally, at a later stage you can set up a script that will be mapping the libraries to users' computers and synchronizing them so that they have local copies.

ODB is intended rather for personal use. If you expect your users to have all the same folder structure, you can use a Powershell script to implement it for every user.

If you want multiple users to collaborate on the folders depending on their permissions/access level, why not use SharePoint site?

You can divide the structure between libraries instead of folders (they give you more options) and after navigating to the site, every user will get a security-trimmed view with only the elements he has access to, e.g:

User A:

|- Group Folders
|- - -Financials (access by: UserA, UserB) 
|- - -Design (access by: User A, UserC) 
|- - -Etc.

|- User folders
|- - -UserA 
|- - - - -Content

User B:

|- Group Folders
|- - -Financials (access by: UserA, UserB) 
|- - -Etc.

|- User folders
|- - -UserB 
|- - - - -Content

In this way a fresh user will always have access to company content and importantly - its updates and new additions.

You can achieve that by navigating to library/list/folder (depending on your choice) sharing settings (List>List Settings>Permissions; Library>Library Settings>Permissions; Folder>...>Shared With>Advanced) and breaking the permission inheritance. Have a look here: https://social.technet.microsoft.com/wiki/contents/articles/36004.restoring-and-removing-item-permissions-in-subfolders-for-sharepoint-online-using-powershell.aspx

Additionally, at a later stage you can set up a script that will be mapping the libraries to users' computers and synchronizing them so that they have local copies.

ODB is intended rather for personal use. If you expect your users to have all the same folder structure, you can use a Powershell script to implement it for every user.

Source Link
grisha
  • 2.8k
  • 3
  • 28
  • 41

If you want multiple users to collaborate on the folders depending on their permissions/access level, why not use SharePoint site?

You can divide the structure between libraries instead of folders (they give you more options) and after navigating to the site, every user will get a security-trimmed view with only the elements he has access to, e.g:

User A: |- Group Folders |- - -Financials (access by: UserA, UserB) |- - -Design (access by: User A, UserC). |- - -Etc.

|- User folders |- - -UserA |- - - - -Content

User B: |- Group Folders |- - -Financials (access by: UserA, UserB) |- - -Etc.

|- User folders |- - -UserB |- - - - -Content

In this way a fresh user will always have access to company content and importantly - its updates and new additions.

You can achieve that by navigating to library/list/folder (depending on your choice) sharing settings (List>List Settings>Permissions; Library>Library Settings>Permissions; Folder>...>Shared With>Advanced) and breaking the permission inheritance. Have a look here: https://social.technet.microsoft.com/wiki/contents/articles/36004.restoring-and-removing-item-permissions-in-subfolders-for-sharepoint-online-using-powershell.aspx

Additionally, at a later stage you can set up a script that will be mapping the libraries to users' computers and synchronizing them so that they have local copies.

ODB is intended rather for personal use. If you expect your users to have all the same folder structure, you can use a Powershell script to implement it for every user.