Skip to content
OpenAppPhysical access, simplified
Login

Max doors per invitation

Type
max_doors_per_invite
Category
Invitations
Enforced at
Authoring-time
Tiers
OrgIntegrationDevice
Enforcement
Enforce
Default
Not configured — no policy cap on portals per invitation.

The number of unique granted portals on an invitation may not exceed max. Extra doors are not silently dropped — the request is rejected.

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
maxintegerYesMaximum unique portals per invitation. 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 across applicable rows. Reject, do not clamp.

Example

An invitation that grants both the lobby and the garage is rejected.

config
{
"max": 1
}

Integrations

This type is documented on these connectors:

The OpenAPI contract names this object InvitationCountLimitPolicyConfig:

{
"max": 1,
"output": "main"
}

max must be positive; requests granting more unique portals are rejected.