Hi, thank you all for the feedback and taking time to think about it. Most of the cases I wrote here are achievable. What I am worried about is that the amount of maintenance work will raise rapidly without haveing implemented usecases for these. See following example of setup: Folder1 - users Backup, A,B,C,D,E Folder2 - users Backup, C,D,E,F,G \ Folder2a - users Backup, C,D,E,F,G,MrX Folder3 - users Backup, A,C,H,J,K,L UC2 reduces lots of confinguring all day around if new folder is needed to create. We migth have more than one Backup machiene and then all backup machienes need to be configured for the new folder. Folder2a would be easy to create and assign additionally only MrX to it. As it is subfolder for Folder2, the users of Folder2 will have access to it without any configuration. UC3 reduces the same configuring overload when the user C no longer needs to have right for syncing the folders. He ofcourse can simply delete the foders and remove the sync. It is clear that if the user C is corrupt and does not follow agreement then there will be trouble. This kind of human factor stays always out of IT to solve. But it will make lot less fuzz when people keep secret documents in synced folder and are ohnest. They might still have some folders that they need to sync and the system takes care of which ones he does have active. I think it is enough when the remote synced folder can be destroyed when user will no longer have right to sync it.