Calendar

Working in the web application

Create events with a title, a time in your time zone (the time follows daylight saving automatically), a place and notes. Recurring events — weekly stand-ups, monthly reports — are set once and expand on their own; a single occurrence can be moved or removed without touching the series.

Invitations go out by mail when you add attendees, and their replies come back into the event. Free/busy lets you see when colleagues are available before you propose a time, as far as their calendars allow.

Shared calendars

A calendar can be shared with other accounts — read-only or read-write — so a team sees the same events in their own calendar applications. What a share grants is set by whoever shares it; the sharing model is in Share and collaborate (a chapter still in preparation).

Connect a calendar application

Native calendar applications — Apple Calendar, Thunderbird, DAVx⁵ on Android, GNOME and KDE calendars — connect over CalDAV:

Point the client at the server and let it discover your calendars (/.well-known/caldav is the standard entry point); if your client wants an explicit calendar URL, your administrator can give you your principal's calendar path. Tasks (to-dos) sync to the same clients as VTODO collections.

Subscribing to someone's public calendar, or to an ICS feed, is done with the calendar's link in your own client — no credentials needed for public links.

What to know

• Invitations travel by mail. Accept, decline or propose a new time from the invitation in your mail application, and the calendar updates.
• Bookable links — a page where outsiders pick a slot in your calendar — are part of the calendar service.