-
Notifications
You must be signed in to change notification settings - Fork 239
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 request] Allow to overwrite event visibility when sharing a calendar #944
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Expected behaviour
Event which is set to "When shared hide this event" should be visible.
Actual behaviour
Currently, because the event visibility can not be overwritten, the event is missing.
User story
My use case is that I have a work calendar which is synced to Nextcloud using a restricted account ("work_account") because I don’t want to give my work systems access to any (private) information that is not required (Principle of least privilege). I then have my regular Nextcloud user ("private_account") to which I have shared the work calendar with edit permissions. The "private_account" bundles all my calendars and I use DavDroid to sync the calendars of this one account with my smartphone. This works nicely because all calendars which are shared with "private_account" automatically appear and I don’t have to setup much when adding a new calendar to get them synced. The only issue is now that events that are set to private in my work calendar don’t end up in my "private_account". I can obviously not change the viability of the event itself because they should be private in my work calendar (not shared with coworkers).
The only workaround for this is for me to setup syncing using the "work_account" on my private devices (DavDroid). This obviously also conflicts with Principle of least privilege because then my private devices would have access to work resources that are not required.
Related issues
Posted there first, then I opened it as a new issue here.
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: