Skip to content
OpenAppPhysical access, simplified
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. Shared row fieldsenforcement (enforce, require_approval,audit_only) and enabled apply to every type;audit_only and disabled rows never block.

NameTypeRequiredValuesDescription
max_secondsintegerYesMaximum length of each invitation schedule slot in seconds. Must be greater than 0.
outputstring or integerNoOptional channel or output id. When set, the policy binds only that output. When omitted, it binds every output of the tier target. A scoped row does not apply when the acting output is unknown.

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.