Holiday calendar
- Type
- holiday_calendar
- Category
- Invitations
- Enforced atWhen this policy is checked: while someone tries to open, while they create or change an invitation or hold, on a membership change or background sweep (lifecycle), or after a denial (record only).
- Access-time
- TiersWhere an admin can set this policy: the whole organization, one integration, or the physical device when the connector supports a device steward.
- OrgIntegrationDevice
- EnforcementEnforcement modes this type accepts. Enforce applies the row. Require approval (user sharing only) opens an admin approval inbox instead of blocking.
- Enforce
- DefaultWhat happens when no row of this type is configured.
- Not configured — no shared holiday date list.
Stores a list of YYYY-MM-DD dates in the organization IANA calendar. Invitation allowed-days rows with holiday_calendar true union these dates into their blackout set. This type has no standalone deny.
When it is enforced
Evaluated when someone opens a door or gate or triggers an entity action. If this policy applies, the open is denied even when roles and grants would otherwise allow it.
Where to set it
Settings → Policies (org), the integration Policies tab, or — on PalGate — the device steward Policies tab.
Policies never grant access. See thepolicies architecture guidefor how org, integration, and device tiers combine.
Arguments
The config object on create/update. Row fields outsideconfig are enforcement (this type acceptsenforce; any other value is rejected with 400), enabled (disabled rows never apply), and capability.
| Name | Type | Required | Values | Description |
|---|---|---|---|---|
| dates | string[] | Yes | — | Array of ISO dates YYYY-MM-DD (organization local calendar). |
| output | string or integer | No | — | Device policies only. One output of the device, as the device reports it (PalGate `1` or `2`, a Shelly, Tasmota, or Waveshare channel index). When set, the policy binds only actions on that output; when omitted, every output of the device. An output that is not one of the device’s outputs, or `output` on an organization or integration policy, is rejected. If an action’s output cannot be identified, an output-scoped policy denies it. |
How overlapping rows combine
Union of dates arrays across applicable rows. Disabled rows contribute no dates. This type never blocks on its own.
Example
With invitation allowed-days holiday_calendar true, a guest cannot open on 1 January or 25 December. Without an allowed-days row, this calendar has no effect.
{ "dates": [ "2026-01-01", "2026-12-25" ]}Integrations
This type is documented on these connectors:
- Home Assistant (home_assistant)
- KNX (knx)
- MQTT (mqtt)
- PalGate Cloud (palgate_cloud)
- Shelly Cloud (shelly_cloud)
- Shelly Websocket (shelly_websocket)
- Tasmota (tasmota)
- Virtual Access (virtual_access)
- Virtual Demo Devices (virtual_demo)
- Waveshare (waveshare)
Related
- Policy catalog
- Policies architecture guide
- Invitation allowed days (invitation_allowed_days)
- Invitation curfew (invitation_curfew)
Typed configuration
Section titled “Typed configuration”The OpenAPI contract names this object HolidayCalendarPolicyConfig:
{ "dates": ["2026-01-01", "2026-12-25"], "output": "main"}dates contains organization-local YYYY-MM-DD values. The calendar has no standalone deny; an invitation allowed-days policy imports these dates when its holiday_calendar flag is true.