Skip to content
OpenAppPhysical access, simplified
Login

Notify on curfew attempt

Type
notify_on_curfew_attempt
Category
Operational
Enforced at
Denial hook
Tiers
OrgIntegration
Enforcement
Enforce
Default
Not configured — curfew denials are not additionally notified.

A denial hook: when invitation curfew blocks an open, OpenApp records policy.curfew.denied and emits on the configured channels. This type does not itself block access.

When it is enforced

Fires after another policy has already denied the action. This type records or notifies; it does not itself grant or deny access.

Where to set it

Settings → Policies (org) or the integration 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
channelsstring[]Yes
audit
Destination channels. Only `audit` is accepted until another channel exists. Unknown names and empty arrays are rejected. Default: ["audit"] (dashboard)
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

Union of channels across applicable rows.

Example

A guest who tries the door at 02:00 during curfew is denied, and Activity shows policy.curfew.denied.

config
{
"channels": [
"audit"
]
}

Integrations

This type is documented on these connectors:

The OpenAPI contract names this object NotificationPolicyConfig:

{
"channels": ["audit"],
"output": "main"
}

Only audit is currently accepted in channels. This notification is a denial hook and does not grant or deny access itself.