Use calendars with Events and Tasks

Calendar identity is persisted for both Events and Tasks. It controls colour, grouping, visibility, and whether the chosen destination accepts writes.

This is the practical result of the Harmonise planning model: calendars organise the plan, Events reserve dates or time, and Tasks track work with a completion state. For example, a Client review Event and Send revised proposal Task can both belong to Work while behaving differently in the plan.

Assigning a Harmonise Task to a Google, Outlook, Apple, Yahoo, or CalDAV calendar does not create a task in that provider. It remains a Harmonise Task.

On mobile

The Event and Task composer headers show the selected calendar. Choose another visible, writable calendar before selecting Create or Save. Standalone Tasks require an explicit calendar from their creation screen.

A Task linked to an Event uses the Event’s calendar. The composer labels that locked relationship From linked event rather than allowing a conflicting destination.

When linking an existing standalone Task, it must already be in the Event’s calendar. Harmonise rejects a calendar mismatch rather than moving the Task as part of linking. A new Task created from an Event uses that Event’s calendar automatically.

On web

The Event form and Task form each include a Calendar choice for standalone items. Choose an editable calendar before saving. A Task linked to an Event uses the Event calendar instead of an independent destination.

Open a saved writable Event and choose Edit event to change its details. A recurring Event may ask which occurrences the change should affect. Read-only Events cannot be edited in Harmonise. The Task inspector provides Edit task for changing an existing standalone Task’s calendar when the destination is editable.

Hiding or filtering a calendar removes its items from the relevant combined view; it does not detach their saved calendar identity.