No invitation re-share

Type

invitation_no_reshare

Category

Invitations

Enforced atWhen this policy is checked: while someone tries to open, while they create or change an invitation or hold, on a membership change or background sweep (lifecycle), or after a denial (record only).

Authoring-time

TiersWhere an admin can set this policy: the whole organization, one integration, or the physical device when the connector supports a device steward.

OrgIntegrationDevice

EnforcementEnforcement modes this type accepts. Enforce applies the row. Require approval (user sharing only) opens an admin approval inbox instead of blocking.

Enforce

DefaultWhat happens when no row of this type is configured.

Not configured — invitees may create further invitations if their roles allow it.

Stops listing residents from creating further invitations. Org and integration rows bind residents (people who are members of a directory listing on the site) by default, not generic members or admins. Device-tier rows without applies_to bind everyone, including admins.

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.

Name	Type	Required	Values	Description
applies_to	string[]	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: Org/integration: resident (a listing member). Device-tier: everyone, including admins.
output	string or integer	No	—	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

Boolean OR across applicable enforcing rows that bind the actor.

Example

A resident of a listing cannot create an invitation from that access. An org admin still can.

config

{}

Integrations

This type is documented on these connectors:

• Home Assistant (home_assistant)
• KNX (knx)
• MQTT (mqtt)
• PalGate Cloud (palgate_cloud)
• Shelly Cloud (shelly_cloud)
• Shelly Websocket (shelly_websocket)
• Tasmota (tasmota)
• Virtual Access (virtual_access)
• Virtual Demo Devices (virtual_demo)
• Waveshare (waveshare)

Related

• Policy catalog
• Policies architecture guide
• No transitive delegation (no_transitive_delegation)
• Who may invite (invite_creator_roles)
• User sharing control (user_sharing)

Typed configuration

The OpenAPI contract names this object InvitationAuthoringPolicyConfig:

{
  "applies_to": ["resident"]
}

Only the optional applies_to field (and output on a device policy) is accepted; {} is valid. A matching actor cannot create or update invitations.