Skip to content
OpenAppPhysical access, fully managed
Login

Invitation allowed days

Type
invitation_allowed_days
Category
Invitations
Enforced at
Access-time
Tiers
OrgIntegrationDevice
Enforcement
Enforce
Default
Not configured — invitation-based access is not limited by weekday or blackout date.

Weekdays are 0–6 with 0 = Sunday. Combination intersects weekday allow-lists (empty intersection means every day is forbidden) and unions blackout dates with holiday-calendar dates when holiday_calendar is true. Local calendar date uses the organization IANA timezone. Checked at invitation redemption and when an invited user who is not an org admin opens an entity. Guests see a hint similar to invitation curfew. Only invitation-based access is ever evaluated: admins and residents opening on their own grants are never bound, and a row whose applies_to omits invitation (and all) never applies.

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.

NameTypeRequiredValuesDescription
weekdaysinteger[]No
0123456
Allow-list of weekdays (0 = Sunday). Omitted means this row does not restrict weekdays.
blackout_datesstring[]No—ISO dates YYYY-MM-DD that invitations cannot use.
holiday_calendarbooleanNo—When true, also forbid dates listed on applicable holiday_calendar policies.
outputstring or integerNo—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

Most-restrictive: intersect weekdays, union blackout_dates, and union holiday dates when holiday_calendar is true. Empty weekday intersection forbids every day. Disabled rows never block.

Example

A guest invitation cannot open on Saturday, on 2026-12-25, or on any date in the org holiday calendar. The guest sees an allowed-days note. The invitation row is unchanged.

config
{
"weekdays": [
1,
2,
3,
4,
5
],
"blackout_dates": [
"2026-12-25"
],
"holiday_calendar": true
}

Integrations

This type is documented on these connectors:

The OpenAPI contract names this object InvitationAllowedDaysPolicyConfig:

{
"weekdays": [1, 2, 3, 4, 5],
"blackout_dates": ["2026-12-25"],
"holiday_calendar": true
}

On a device policy, output limits the row to one output of that device. weekdays uses Sunday = 0 through Saturday = 6. Dates use the organization-local YYYY-MM-DD calendar. Each field is optional for a row; holiday_calendar: true imports dates from applicable HolidayCalendarPolicyConfig rows.