Who may invite
- Type
- invite_creator_roles
- 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 — anyone who can otherwise create invitations may do so.
The actor must match any remaining role after intersecting allow-lists. This type is not admin-exempt: omit admin and admins cannot invite. Compose with user_sharing — both must pass; user_sharing mode none still wins. Dashboard presets include admin, integrations:update, resident, and technician; other role strings are allowed.
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 |
|---|---|---|---|---|
| allowed_roles | string[] | Yes | adminintegrations:updateresidenttechnician | Non-empty allow-list of role strings. Presets are listed; custom role keys are also accepted. |
| 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: Every author, 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
Intersection of allowed_roles. Empty intersection means nobody. Not admin-exempt.
Example
A technician cannot create an invitation. A resident still can, unless user_sharing also blocks them.
{ "allowed_roles": [ "admin", "resident" ]}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
- User sharing control (user_sharing)
- No transitive delegation (no_transitive_delegation)
- No invitation re-share (invitation_no_reshare)
Typed configuration
Section titled “Typed configuration”The OpenAPI contract names this object InviteCreatorRolesPolicyConfig:
{ "allowed_roles": ["admin", "resident"], "output": "main"}allowed_roles is a non-empty role allow-list. Applicable rows intersect their lists; an empty intersection allows nobody.