-
Notifications
You must be signed in to change notification settings - Fork 669
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
Feature Settings Locking for Managed User Deployments #1744
Comments
This feature sounds very enterprise centric. As of today we are already partially able to remove these options within the client themes. This should be enough to fulfill this request? Von Samsung Mobile gesendet -------- Ursprüngliche Nachricht -------- As an ownCloud administrator, I want to be able to lock down certain ownCloud sync client features so that end users cannot make changes to them, and complicate management of the ownCloud deployment or break their client. For example: Disable the ability to add more sync folders than already exist — |
Additional information as communicated by @msrex The current branding based approach is not enough. There is the need to change these settings during live operations. My thoughts: |
It could be combined with remote wipe, but it is definitely a different user story. More to come on feature / function here. |
User story whise true - technically the same direction |
As an ownCloud administrator, I want to be able to lock down certain ownCloud sync client features so that end users cannot make changes to them, and complicate management of the ownCloud deployment or break their client.
For example:
@dragotin @danimo Future concept...
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2038338-feature-settings-locking-for-managed-user-deployments?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: