Skip to content
OpenAppPhysical access, simplified
Login

Default share uses

Type
share_default_max_uses
Category
Invitations
Enforced at
Authoring-time
Tiers
OrgIntegrationDevice
Enforcement
Enforce
Default
Not configured — omitted share max_uses stores 1.

Create never omits max_uses for shares unless the author chose unlimited and policy allows it. If the client omits max_uses, the effective default applies (this policy, combined as the minimum of configured defaults, otherwise 1). A child cannot raise a parent’s default. Write is rejected if the default is greater than the effective finite share_max_uses 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_usesintegerYesDefault redemption count when the author omits max_uses. 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 default rows.

Example

Creating a share without max_uses stores 2 opens instead of 1.

config
{
"max_uses": 2
}

Integrations

This type is documented on these connectors: