You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature request : to be able to share only busy/available information when sharing a calendar or all events without details.
This would be a great way for example to see limited information of my private agenda on my professionnal computer / system / calendar client.
Steps to reproduce
Click on a calendar sharing button
Tick a box to select "not sharing details / only share busy-available information"
Get a public link to share the calendar / subscribe to it without the events details
Expected behaviour
Just like the current sharing functionnality, but one can only see basic information on the calendar events : only start and end of each event (no text, no invitees, no location or category or reminders or whatever).
Actual behaviour
There is no such functionnality as of now
Server configuration
Not applicable. It would have to work just like the current sharing functionnality.
The text was updated successfully, but these errors were encountered:
Please use the Github Reactions feature instead of commenting +1, 👍 etc. These kinds of comments just unnecessarily notify everyone subscribed to this issue. Thx! :)
This is a feature request : to be able to share only busy/available information when sharing a calendar or all events without details.
This would be a great way for example to see limited information of my private agenda on my professionnal computer / system / calendar client.
Steps to reproduce
Expected behaviour
Just like the current sharing functionnality, but one can only see basic information on the calendar events : only start and end of each event (no text, no invitees, no location or category or reminders or whatever).
Actual behaviour
There is no such functionnality as of now
Server configuration
Not applicable. It would have to work just like the current sharing functionnality.
The text was updated successfully, but these errors were encountered: