-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Overview: Calendar Sharing #20096
Comments
cc @tcitworld |
One of the biggest issue when it comes to publishing is that each calendar is limited to one publishing link. This is causing many issues that you can't simply revoke a calendar without breaking embedded calendars / having to send out a new public link to people who should still have access. In order to solve any of the publishing related tickets mentioned above, we first need support for multiple publishing links. Once we have support for that, adding support for more sharing types including "internal busy", "public busy", "public editable", "public busy editable" should be straight forward. |
Once we have support for these public types, adding password-protected public shares or shares with expiration-link would also be straight forward. |
Overall tasks:
|
also cc @raimund-schluessler @skjnldsv This will require changes to |
Can |
Not as far as i can tell. We would have to move to our own implementation. |
Hi. I suggest to add also a link to issue "Send invitations for shared calendars" #26668 , as it is about shared calendars expected features. |
This overview of calendar sharing issues could also reference #5050 issue about sharing from MacOS Calendar.app. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I suggest to add #19994 (as mentioned in the this issue, the problem still occurs in our installation, NC Version 26.0.4) |
This is an overview ticket for feature requests / bugs related to Calendar Sharing:
Sharing
Publishing
Features missing for feature parity with file-sharing:
The text was updated successfully, but these errors were encountered: