Skip to content
OpenAppPhysical access, simplified
Login

Max invitation uses

Type
invitation_max_uses
Category
Invitations
Enforced at
Authoring-time
Tiers
OrgIntegrationDevice
Enforcement
Enforce
Default
Not configured — unlimited-use invitations are allowed.

Invitations must have a finite use count. Omitting max_uses (unlimited) is rejected, and a count above the cap 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
max_usesintegerYesMaximum redemption count. 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_uses across applicable rows. Reject, do not clamp.

Example

An invitation with no use limit, or with 50 uses, is rejected.

config
{
"max_uses": 10
}

Integrations

This type is documented on these connectors:

The OpenAPI contract names this object InvitationMaxUsesPolicyConfig:

{
"max_uses": 10,
"output": "main"
}

max_uses must be positive; unlimited invitations are rejected when this policy applies.