OdooWiki OCA HUB

Readonly publishing of calendars

base_ical folder_open OCA/server-backend open_in_new
Tools License: AGPL-3

This module allows administrators to configure iCalendars based on an arbitrary selection on arbitrary models.

Users can selectively subscribe to them by enabling them in their profile form.

This is useful for exposing Odoo data to calendaring application like Nextcloud.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets administrators publish read-only calendar feeds (.ics URLs) from any Odoo model, and lets users subscribe to those calendars from their profile.

Administrators can define calendars under the iCalendars menu (Settings area). Each calendar picks a model, a filter domain, and either a simple mapping of fields to calendar properties (DTSTAMP, UID, DTSTART, DTEND, SUMMARY) or an advanced Python snippet for full control. A live preview and a help tab show available variables.

Users see a Calendars tab on their profile where they can generate a personal URL for each calendar they are allowed to use. The URL contains an access token and can be pasted into external calendar apps such as Nextcloud. Existing tokens are listed and can be deleted.

Business rules: calendars can be marked as automatic, in which case they are enabled for all current and future users, optionally restricted to selected groups. The domain and expressions are validated when saved. The feed is served read-only over HTTP and supports conditional requests (304 Not Modified). Only internal users can create URLs, and each URL is tied to the calendar it was generated for.

Depends on

web

Menus it adds

menu_ical
Models and fields (4)
  • base.ical · new modelauto (Allow automatically), code, mode (_get_operating_modes), name, model (Model Name), active, domain, preview, model_id, help_text, auto_group_ids (Groups), expression_uid (UID), expression_dtend (DTEND), allowed_users_ids, expression_dtstamp (DTSTAMP), expression_dtstart (DTSTART), expression_summary (SUMMARY)
  • res.users · extends an existing modelical_ids
  • base.ical.url.show · new modelid, url
  • base.ical.url.description · new modelname (Description), calendar_id

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

Sources · Odoo 15.0

Confirmed on 2026-11-03 in branch 15.0 of OCA/server-backend.

terminal Installation and usage

OCA documentation · Odoo 18.0

To configure this module, you need to:

  • Go to Settings/Technical/iCalendars
  • Create a iCalendar, fill in the model you want to expose and possibly a domain to restrict records. You can use the user variable to restrict things relative to the user using the iCalendar
  • A iCalendar is only available to the allowed users. Use the Allow automatically to make the iCalendar available to all users
  • See the examples below for a start

Examples

Simple example, for model calendar.event, you'd fill in record.allday and record.start_date or record.start as DTSTART and record.allday and record.stop_date or record.stop as DTEND.

Advanced example, for model calendar.event, you'd use calendar = record._get_ics_file() in the code.

Advanced example, for model hr.leave, you can use the following code and [("employee_id.user_id", "=", user.id)] in the domain to export the own time offs. This is a bit more complex because of the way Odoo handles the begin and end times of leaves, and you'll want the extra day as most clients interpret the end date as non-inclusive.:

confirmed = ("validate", "validate1")
if record.request_unit_half or record.request_unit_hours:
   event = {
      "dtstart": event["dtstart"].date(),
      "dtend": event["dtend"].date() + timedelta(days=1),
   }
else:
  event = {
      "dtstart": record.date_from,
      "dtend": record.date_to,
   }

event["summary"] = record.name
event["status"] = "CONFIRMED" if record.state in confirmed else "TENTATIVE"

Advanced example, for model mail.activity, you can use the following code and [("user_id", "=", user.id)] and domain to export all user activities.

todo = {
   "summary": record.display_name,
   "due": record.date_deadline,
   "description": html2plaintext(record.note) if record.note else ""
}

To use this module, you need to:

  • Go to your profile form
  • Click Enable on one of the calendars listed in tab Calendars
  • Copy the URL to the application you use

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.