Hr holidays calendar events privacy
This module allows to redefine the privacy level of calendar events created from Time off requests.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Lets you choose the privacy level (Public, Private, or Only internal users) for calendar events created from each Time Off type, so leave events are not always visible to everyone.
When a Time Off request is approved, Odoo creates a calendar event for the employee. This module adds a new setting on each Time Off type so you can decide how visible that event should be.
On the Time Off type form (the screen where you configure types such as Paid Time Off or Sick Leave), a new field called "Calendar event privacy" appears after the Time type field. You can pick one of three values:
- Public: everyone can see the event details.
- Private: only the employee sees the details; others see it as busy.
- Only internal users: internal employees can see the details, but not external users.
The default value is "Only internal users", so newly created Time Off types are not fully public unless you change them.
When a leave request is confirmed and its calendar event is prepared, the module automatically applies the privacy level configured on the leave type to that event. This means the visibility of the event follows the Time Off type, without the employee having to set it manually.
The module extends the Time Off request model (hr.leave) and the Time Off type model (hr.leave.type), and adds the new field to the existing Time Off type form view.
Depends on
Models and fields (2)
- hr.leave · extends an existing model
- hr.leave.type · extends an existing modelcalendar_event_privacy
Text generated by AI (DeepSeek) from reading the Odoo 15.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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/hr-holidays.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
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.