Syncing elementary OS Calendar and Tasks with Google Calendar

Keeping appointments in elementary OS Calendar and recording follow-up items in Tasks is straightforward once the app knows where your information lives. Google Calendar is the usual meeting and schedule destination, while Google Tasks remains a separate Google service. The distinction matters because an event added to Google Calendar and a task added to Google Tasks do not automatically become the same kind of synchronised record.

elementary OS connects to Google Calendar through its account framework and the CalDAV calendar service. That connection can carry event times, locations, notes, attendees and recurrence between Google and the desktop. It is a good fit for households, Australian community groups and small businesses that already keep a shared Google schedule, even when their members use several different devices.

Task syncing needs a separate check on your installed release. Tasks in elementary Calendar can be held in local or provider-backed lists, while Google Tasks does not reliably appear as a two-way CalDAV task list. This guide shows how to connect events, test the boundary, and choose a sensible workflow for tasks without creating duplicates or deleting work from either side.

Choose the right synchronisation method

Start by deciding whether you need shared events, shared tasks or both. The Google account route is the most complete option for calendar events because it creates a live two-way connection. A file import creates a one-time copy, and an internet subscription can provide a convenient read-only view. Neither file method keeps future edits in step with Google.

The practical choices compare as follows:

For most people, add Google as an online account and use its calendars inside Calendar. Keep a local elementary task list for personal follow-ups, then manage Google Tasks separately in the Google interface. If an organisation already supports a standards-based task server, that may be preferable for shared assignments, provided the current elementary release connects to it cleanly.

Before moving a busy calendar, create one disposable event and one test task. The event check confirms account, CalDAV and display settings; the task check reveals whether task data is being exposed by the provider. This small test prevents a production calendar from becoming a troubleshooting exercise.

Connect Google Calendar to elementary OS

Update elementary OS first, preferably through AppCenter, then confirm that Calendar opens without an account error. Updating the system, Calendar and account components reduces the chance of an old calendar backend failing against a current Google login page. If the machine is managed by a school or employer, check its update policy before changing packages.

Open Settings, choose Online Accounts, select Add Account and pick Google. A browser window opens for Google’s sign-in flow; complete it there and approve the requested calendar permissions. Accounts with two-factor authentication may ask for a device code or verification through an approved app. If the account page offers service choices, enable Calendar and leave unrelated services disabled. elementary OS uses the resulting authorisation for the Google calendar service, so the account password does not need to be stored in Calendar.

Launch Calendar and look for the new Google account in its calendar chooser. Select the calendars you want, including shared and work calendars, and set the one you use most as the default. Allow several minutes for the first population, then restart Calendar if events remain absent. Compare a simple event with one containing attendees and reminders, since Google-specific colours, conference details and alert timing can differ between clients.

For shared calendars, inspect their coloured names rather than assuming every subscribed list is writable. A calendar shared as read only can still display events, but changes such as moving or deleting an entry may be refused. If Google marks the connection as read only, ask the calendar owner to grant suitable access instead of repeatedly removing and re-adding the account.

Set up task lists without losing changes

Depending on the elementary OS release, tasks may be presented in the task pane of Calendar or through a companion Tasks interface. Open the task view before deciding that a Google task is missing. A local list can still work normally for shopping lists, renewal reminders and household jobs. A due date on a task does not automatically make it a scheduled event on Google Calendar.

Google Tasks is a separate data store, not a normal event on Google Calendar. Its task lists are not consistently exposed through the Google CalDAV account used by elementary Calendar, so two-way syncing should not be assumed. Open Google Tasks, select a disposable item and wait for a refresh in elementary. If it does not appear, the account connection is carrying events rather than Google task lists.

There are three workable responses. Keep a personal list inside elementary and copy over anything urgent. For shared work, use a task service that your organisation already supports, such as a Nextcloud or other CalDAV task collection when the installed release can authenticate against it. Where Calendar offers an internet-calendar option, Google’s ICS link for tasks can create a read-only feed that may appear as all-day entries; edits made in elementary will not travel back, and the feed may not refresh perfectly.

Label local and shared lists clearly. For example, use “Personal follow-up” for household actions and “Google team” for items copied from Google Tasks. Avoid opening the same Google calendar through both an account connection and an imported ICS file, because identical events can then appear twice. Keep a note of which list receives each new item so later changes do not become ambiguous.

Match Australian calendars and time zones

Australia needs careful attention to zones and daylight saving. Sydney, Melbourne, Canberra and Hobart use Eastern Time, shifting between AEST and AEDT; Brisbane stays on AEST throughout the year; Adelaide uses a half-hour offset in ACST or ACDT; and Perth uses AWST. The displayed offset and the event’s own time zone both matter when a calendar is shared between states.

Recurring meetings can drift when a rule is tied to local time rather than an exact instant. For a weekly Sydney appointment, local-time recurrence is usually what you want, so it remains at the same clock time after the daylight-saving change. For a flight from Melbourne to Perth, decide whether the entry represents a fixed departure moment or a local time that should remain aligned with the origin city.

Use separate calendars for Australian public holidays because dates differ across states, and rename them with the jurisdiction, such as “NSW public holidays” or “Victoria public holidays”. Official state government feeds can be subscribed where available. Community organisers may also maintain calendars for AFL or NRL fixtures, school term dates, council events and local markets.

Google Workspace is widely used by Australian small businesses, schools and community organisations, often alongside Microsoft 365. A shared calendar should therefore follow the organisation’s established account rather than create a second private diary. If Microsoft Exchange calendars must remain visible too, confirm that the account configuration can handle that additional provider before changing defaults.

Keep the connection reliable and private

Treat the Google connection as a live database link, not a folder of downloaded documents. Check the calendar list in Google Calendar, ensure the relevant calendars are enabled, and leave enough time for the desktop app to refresh. If notifications do not sound, check Calendar’s notification permission in Settings and make sure the desktop notification service is running.

Duplicates often come from adding the same calendar twice, while missing events can result from a stale login token, an unselected calendar or a workplace policy that blocks third-party authorisation. Restart Calendar before removing and re-adding the account. Never delete an event merely as a refresh test, because deletion can propagate to Google and everyone invited to it. Check both services before removing an item you believe is unwanted.

For security, keep Google two-factor authentication enabled and review third-party access in the Google account’s security settings. Removing the Google account from elementary OS should discard its local access; if the service remains active, use Google’s third-party connections page to revoke it. In a managed Australian school or business, ask the administrator before authorising an account, because the organisation may require a particular Workspace account or restrict access to external calendars.

Create a test event named “Calendar sync check” in Google Calendar and wait for it to appear in elementary Calendar before importing any live calendar.