-
Notifications
You must be signed in to change notification settings - Fork 663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Selective Sync] Push default selective sync policy to client? #2517
Comments
+1. Having an option to not sync newly shared content would be great. Giving an admin the ability to set a default set of selections that get pushed out to users would be awesome. Any time steps need to be repeated from one installation to the next or where an admin needs to provide steps to a user to get to a useful configuration is an opportunity for automation and an improved user experience. |
This doesn’t need to be an option. New shares should never automatically be synced before they are accepted. On the server side we will introduce a page for pending shares: owncloud/core#13495 |
Same for mobile of course too. We need to look at the architecture for these sorts of communications. |
Yep, the mobile apps would have it in the »Transfers« view, up top. |
Ok. Good for the roadmap conversation. |
This feature would be a big benefit. Especially with external storages this is a pain in the a.. if they are automatically downloaded from the server. |
1st step is #6761 |
I am extremely happy with the new Selective Sync feature, so thanks for this big improvement!
However, I am wondering if it is possible to push a default selective sync policy to the client, somehow?
What I would like to achieve is that users which are invited to a shared folder do not automatically download this shared folder to their computer first, then decide they do not want this and then have to go to their Selective Sync configuration and turn this off.
So I would like to do the following: I share a folder "Projects" with users, containing subfolders "Project A", "Project B" and so on. All new folders should not be synchronized to clients by default. Users can see which projects there are, and then decide to want to sync one of them, e.g. "Project B" because they are actively working on it.
Typical application would be that there are 100 folders under "Projects" of which only a few are relevant and need to be synced.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: