I strongly recommend having a separate odrive folder for each user and using the default locations that are created during the initial odrive run for that user.
Chances are that each family member is working on different files, which odrive facilitates better than anyone else with “progressive sync”. You’ve probably already seen this in action, but odrive allows you to sync exactly what you need and nothing more. So, each user can navigate directly to the file they need and work on that specifically, without downloading anything else. This is different than Dropbox, where everything is downloaded by default, regardless of if you need it or not. The result is that you only have duplicate data if users are working on the same exact files.
I realize there may be instances where users will want to access the same files (shared media, for example), but I can’t recommend pointing separate user instances of odrive all to the same odrive directory. Honestly I’ve never tested it, so I can’t say for certain what the result would be. Just off the top of my head, I can imagine some trouble when dealing with placeholder files.
For example, user A expands folder1, and placeholder files are laid down. User B’s odrive instance now sees a new folder appear and foreign placeholder files (it did not create these). Since it did not create the placeholder files it remove s them and lays down its own. User A’s odrive instance may see the removal of the placeholders before the new placeholders are put down and see that as a delete of the file. The item will end up in the odrive trash for user A. Then it will pick up the new placeholder file that User B’s instance put down and see that as foreign and delete it… etc… etc… Since this would be timing-based, it may eventually work out, but I can’t say for certain.
So, bottom line is: don’t smash all the odrive instance folders together. The good news is that odrive has enough safeguards that you shouldn’t lose any data, even with the different instances trying to reconcile all of the foreign local changes that are happening. You could end up seeing stuff randomly appear in odrive trash, though, and other strange behavior…