Browse documentation

Events

Create timed or all-day commitments, add useful details, and keep your calendar current.

Events are the places you need to be and the commitments that occupy your calendar, not the work you need to finish.

An Event can be a Sunday football match, a project review, a dentist appointment, a birthday, or a conference. It always belongs to a calendar and has either exact start and end times or one or more all-day dates.

Harmonise keeps Events beside Tasks without pretending they are the same kind of thing. Together, Events and Tasks are your Plans. Open All Plans when you want to see both sides of that picture.

What makes something an Event?

An Event answers: When is this happening? It reserves time or marks a date, but it does not have a completion checkbox.

Use an Event for meetings, appointments, classes, matches, calls, birthdays, trips, and other commitments tied to a date or time. Use a Task when the important question is: Have I finished this?

Event or Task?

The distinction becomes clearer when the two appear together:

Situation Harmonise item
Sunday football from 8:00-10:00 AM Event
Wash the football kit before Sunday Task
Project review on Monday Event
Prepare the figures before the review Task
Dentist appointment at 2:00 PM Event
Call the dentist to confirm Task

Sunday football is an Event because it happens at a set time. Washing the kit is a Task because it is work that needs to be finished before the Event.

Start with the commitment

An Event needs a title, a calendar, and its timing. Design review is enough of a title; Thursday from 10:00-11:00 AM explains when it happens; Work explains where it belongs.

Add a description, location, reminders, repeat rule, or linked Tasks only when they help. A useful Event does not need every available field.

Every Event belongs to one eligible, writable calendar when it is created. The calendar gives the Event a home, colour, visibility, and sync destination. Calendars marked Read-only can provide context but cannot receive a new Event or accept edits from Harmonise.

Timed and all-day Events

Use a timed Event when a commitment reserves exact hours. Use an all-day Event when it belongs to one or more dates without reserving a clock-time block.

Scenario Event type Result
Dentist appointment, 2:00-2:45 PM Timed A 45-minute block appears at that time in Agenda.
Birthday on one day All-day The birthday stays attached to the date without occupying working hours.
Conference from Monday to Wednesday Multi-day all-day The Event spans all three calendar dates.

A timed Event’s end must be later than its start. An all-day Event uses an inclusive date range: its final date can be the same as its first date or later. A one-day all-day Event is valid.

Every Event has one immutable IANA timezone, selected when it is created. Moving the Event does not change this timezone. Timed Events are stored as exact moments interpreted with that timezone. All-day Events keep their local dates in that timezone. Viewing or editing the Event from another timezone does not replace the Event timezone.

A complete Event example

Here is one Event with enough detail to be useful:

Design review

  • Calendar: Work
  • Date and Time: Thursday, 10:00-11:00 AM
  • Location: Meeting room 3
  • Reminder: 15 minutes before
  • Linked Task: Prepare the figures

The calendar controls where the Event appears. The time reserves the hour, the location keeps practical context with the commitment, and the reminder provides notice. The linked Task keeps the preparation work separate but connected.

On mobile

  1. Open the Create menu and choose Event.
  2. Enter Design review as the title.
  3. Choose the calendar name in the header, then select Work.
  4. Set Thursday from 10:00 AM to 11:00 AM and leave All-day off.
  5. Open Location and enter Meeting room 3.
  6. Add a reminder for 15 minutes before.
  7. Add a repeat rule or linked Tasks when needed.
  8. Choose Create.

For a date without exact hours, turn All-day on and choose its first and final dates. Use the same date twice for a one-day all-day Event.

Some core Event creates can be accepted locally and synchronized later. This depends on the local Event save being available, the operation being a supported Event-only change, and the calendar being locally manageable. Events with attachments, managed online meetings, invitations, linked Tasks, or other server-owned work may need a connection instead. See Offline and synchronization behavior below.

On web

  1. Choose Create, then choose Event.
  2. Enter Design review and set Thursday from 10:00-11:00 AM.
  3. Leave All-day off and choose Work under Calendar.
  4. Enter Meeting room 3 under Location.
  5. Add the 15-minute reminder.
  6. Add a repeat rule or linked Tasks when needed.
  7. Choose Create event.

Harmonise starts with an available writable calendar unless you choose another one. Open the Event later and choose Edit event to change its details.

Add the details that help

Calendar

Choose the calendar that best explains where the Event belongs. Hiding a calendar removes its Events from combined planning views without deleting them. Moving an Event requires the target calendar to be writable.

For a connected Event, the calendar name and colour identify its source. Provider sign-in and permissions are handled by the calendar connection; Harmonise does not display the provider password or credentials in Event details.

Creating, changing, or deleting an Event on a writable connected calendar is written through after the Harmonise save succeeds. Network or provider processing can delay when the change appears elsewhere. A read-only connected Event must be changed in the calendar that owns it.

If an account is disconnected or its calendar connection is not set to Sync, its existing Events stop receiving current provider updates. Reconnect or re-enable the connection instead of recreating Events, which can produce duplicates. If an expected Event is missing from an enabled connection, choose Sync now.

Date, time, and timezone

Use exact start and end times when the commitment occupies hours. Use All-day for one or more inclusive local dates. Review both dates after switching between timed and all-day because the two types use different time models.

Location and description

Use the location for the place you need to reach. Use the description for an agenda, access instructions, or other context that belongs with the Event. When a saved location supports it, Event details also provide Open in Maps.

Participants and responses

An Event can have an organizer and participants. An invited participant can be awaiting a response, accepted, tentative, or declined. An invited Harmonise user can respond to an eligible invitation using the response controls available for that Event.

Accepting, choosing tentative, or declining changes that participant’s response only. One participant declining does not cancel the Event for everyone. Participant information is shown subject to Event access and profile privacy rules. The Event remains saved even if a best-effort notification delivery does not succeed.

On mobile and web, the current Event invitee pickers use preview or mock People and Groups choices rather than a dependable production invitation workflow. Treat invitee selection on both platforms as limited while this is being completed. Existing participants and supported RSVP controls can still appear from real Event data; email or calendar-provider invitation delivery is not guaranteed for every deployment.

Online meeting

Depending on the deployment and the connections available to you, an Event can use a managed meeting from Google Meet, Zoom, Discord, or Microsoft Teams. You can also add a manually supplied HTTPS meeting URL, including a custom HTTPS URL that passes Harmonise’s safety checks.

Provider choices appear only when the provider is enabled and connected, and the Event timing and provider capabilities support the choice. The Event’s calendar account and meeting-provider account can be different. Changing the Event calendar does not automatically change the selected meeting connection.

An Event can keep both a physical location and an online meeting. Creating or changing a managed online meeting requires an internet connection. A manually pasted meeting link is stored with the Event but is not remotely managed by Harmonise.

Attachments

An Event can have up to five attachment slots. Attachments belong to the Event or to the recurring Event series, not separately to each occurrence. Occurrences in the same series share that Event attachment collection.

Editing, moving, cancelling, or deleting only one occurrence does not remove the series attachments. Deleting the complete Event series removes its Event attachments through the normal deletion process. When you split a series with This and following occurrences, the earlier source series keeps its existing attachments, while the new future series starts without copied attachments.

Event attachments are stored in Harmonise and are not copied to Google Calendar, Outlook, Apple Calendar, or another calendar provider. Files require an internet connection to upload, and only files that finish processing successfully become available. Event attachments are currently private to the Event owner.

Reminders

An Event can have up to two active reminders. Reminders are valid for timed, one-day all-day, and multi-day all-day Events.

A reminder must be at the Event time or a supported non-negative offset before it. Zero means at the Event time for a timed Event or on the Event date for an all-day Event. For an all-day Event, other offsets are measured from the Event’s first local date in the Event timezone. Harmonise preserves that relative meaning instead of treating the date as an arbitrary midnight in UTC. Moving the Event recalculates its reminders from the new time or first local date.

Event reminders are separate from reminders on linked Tasks. A linked Task can keep its own deadline and scheduled-start reminder rules.

Remove an existing reminder before adding another when the two-reminder limit is reached. A saved Event reminder is an alert; it is not an ordinary Inbox item.

Repeat

Use Repeat when the commitment follows a regular daily, weekly, monthly, or yearly pattern. Recurring changes can affect one occurrence, this and following occurrences, or the entire series. Harmonise shows only scopes that can be applied safely; an online meeting or provider-managed recurrence can reduce the choices. See Recurring Events before making a broad series change.

Linked Tasks

Add a linked Task when work must be completed by the Event. The Event supplies the Task’s effective deadline and calendar while the Task keeps its own completion state, schedule, reminders, subtasks, and other Task-owned details. A new Task created inside an Event uses the Event calendar and timezone. An existing Task can be linked only when it already uses the Event calendar; link or relink operations align its stored Task timezone with the Event timezone. While the Event relationship controls the Task, the Task does not expose a separate timezone choice. See Events and linked Tasks for the complete workflow.

Offline and synchronization behavior

Harmonise can save some core Event changes locally and synchronize them later. This is not universal offline support. Eligibility can depend on whether Harmonise can save the Event locally, whether the operation is a supported Event-only change, whether the Event belongs to a locally manageable calendar, and whether the Event has a conflict or another synchronization barrier.

Attachment file actions, managed online meetings, invitations and RSVP side effects, provider-owned calendar changes, and other server-owned side effects still require a connection. A local save is not complete provider synchronization; check the Event after the connection is restored.

After you create an Event

On mobile, select a date on Home and use Events, Agenda, or All Plans to see its commitments. On web, use Month for a broad calendar or Agenda for a week timeline. Selecting an Event opens its details.

Open an Event and choose Edit event to change its title, calendar, timing, location, description, reminders, repeat rule, participants, online meeting, attachments, or linked Tasks. A recurring Event may first ask which occurrences the change should affect, but meeting state and provider rules can reduce the available scopes.

Mobile uses the Event detail view and the full Event composer. Web opens Event details in an inspector and edits through the Event edit flow. The fields are not displayed identically on both platforms.

The Event detail view can include its calendar, Event dates and times, immutable Event timezone, location, description, reminders, recurrence, linked Tasks, participants and RSVP state, online meeting, attachments, activity or update history, and read-only or unsupported-recurrence warnings.

Deleting an Event deletes every Task whose Event link is still present when deletion begins. A Task detached or unlinked beforehand is standalone and remains. Deleting a Task does not delete its Event. The Event operation supports Only this occurrence, This and following occurrences, and Entire series, but the current mobile and web deletion dialogs expose only Only this occurrence and Entire series. The middle scope is therefore not available from every platform or every Event. Editing scopes are separate and may still offer This and following occurrences when it is safe.

Saved changes appear on other signed-in devices and writable connected calendars after Harmonise finishes syncing. If a core change was accepted locally, it can remain pending until a connection is available; server-owned side effects still need an active connection.

Events and Tasks together

Events tell you when something is happening. Tasks tell you what still needs to be done.

For example, Project review is an Event because it happens on Monday at a set time. Prepare the figures is a Task because it must be finished before the review. Linking them keeps the preparation attached to the commitment.

A Task linked to a timed Event uses the Event start as its effective Due Date and Time. A Task linked to an all-day Event uses the Event’s first local date as its effective Due Date. Moving the Event recalculates eligible deadline reminders, but does not move the Task’s Scheduled Date or Scheduled Date and Time or its scheduled-start reminders. A Task schedule is allowed to remain after the Event-controlled deadline. The frontend may show a non-blocking warning, but saving is not blocked; reschedule the planned work only if you want it to happen earlier.

Event reminders and linked Task reminders remain separate.

Common problems

I cannot choose a calendar

Make sure the calendar is eligible and writable. A calendar marked Read-only cannot receive the Event. Check your default calendar, then choose another writable calendar if needed.

The Event time is rejected

For a timed Event, make sure the end is later than the start. For an all-day Event, make sure the final date is the same as or after the first date.

My reminder did not arrive

Confirm that the Event saved, the reminder still appears in Event details, and Harmonise has notification permission. Delivery can require a working connection and a configured notification service.

A linked Task is scheduled after the Event

That state is valid. Moving the Event changes the linked Task’s effective Due Date or Due Date and Time, but not its Scheduled Date, Scheduled Date and Time, or scheduled-start reminders. Harmonise may show a non-blocking warning; saving the Event is not blocked.

A connected Event is missing or cannot be edited

Confirm that its calendar is connected and has Sync enabled; it can remain hidden while updates continue. A read-only Event cannot be changed in Harmonise. Choose Sync now for a sync-enabled connection. If the connection is interrupted, reconnect it rather than recreating Events and risking duplicates.

My changes have not appeared on another device

Check that the save finished, reconnect both devices, and refresh the planning view. Do not clear local browser or app data while a change is still waiting.

Next steps