Skip to content
OpenAppPhysical access, fully managed
Login

Emergency lockdown

Type
emergency_lockdown
Category
Operational
Enforced at
Access-time
Tiers
Org
Enforcement
Enforce
Default
Not configured — no lockdown.

When active is true, non-admin principals cannot perform inbound cloud opens (and similar writes) on openings that are not classified means_of_egress or fire_door_assembly. Admins remain able to act. Egress and fire-door classes skip this deny so lockdown cannot electrically trap people. This policy never sends PalGate output-disable and never replaces listed exit hardware. Set active to false to lift the lockdown without deleting the row. The row is org-wide: `active` is its only config field, and `output`, `applies_to`, and a capability scope are rejected.

When it is enforced

Evaluated when someone opens a door or gate or triggers an entity action. If this policy applies, the open is denied even when roles and grants would otherwise allow it.

Where to set it

Settings → Policies (org).

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.

NameTypeRequiredValuesDescription
activebooleanNo—When true, deny non-admin inbound cloud opens on ingress-classified openings. When the field is present it must be a boolean; an enabled row without it is active. Default: true

How overlapping rows combine

Boolean OR of active across applicable enforcing rows.

Example

Guests, agents, and members cannot open ingress doors from the cloud. An organization admin still can. Means of egress and fire-door openings are not denied by this policy. Listed exit hardware is unchanged.

config
{
  "active": true
}

Integrations

This type is documented on these connectors: