Skip to content
OpenAppPhysical access, fully managed
Login

Max invitation duration

Type
invitation_max_duration
Category
Invitations
Enforced at
Authoring-time
Tiers
OrgIntegrationDevice
Enforcement
Enforce
Default
Not configured — no policy cap on invitation slot length.

Each schedule slot on create or update may last at most max_seconds. The request is rejected rather than silently shortened. The invitation create wizard shows the effective cap.

When it is enforced

Evaluated when someone creates or updates an invitation, hold, or share. Requests that would exceed the limit are rejected — they are not silently rewritten.

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
max_secondsintegerYes—Maximum length of each invitation schedule slot in seconds. Integer from 1 through 31536000 (365 days).
applies_tostring[]No
adminmemberresidentall
Principal kinds this row binds, as a non-empty array of admin, member, resident, all. Other kinds, a bare string, and empty arrays are rejected. `all` matches every kind this policy can bind. A caller is every kind it is at once, and a row binds when any of them is listed. When omitted, the default applies. Default: Every author, including admins.
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

Minimum of max_seconds across applicable rows. Reject, do not clamp.

Example

Creating a 48-hour invitation is rejected. A 8-hour slot is accepted.

config
{
"max_seconds": 86400
}

Integrations

This type is documented on these connectors:

The OpenAPI contract names this object InvitationMaxDurationPolicyConfig:

{
"max_seconds": 86400,
"output": "main"
}

max_seconds must be positive. Requests exceeding the effective cap are rejected rather than shortened.