Access Control events provide a record of all access attempts, door status changes, alarms, and security-related activities within the system. These events are displayed in Access History and can also trigger notifications or alarms based on your system configuration.

Authorized Access

An Authorized Access event is generated when a user successfully authenticates and is granted access to a door or access point. The user must have valid access permissions and need to have at least one of the access types enabled for them.

• Click-to-Access (Mobile BLE)
• Tap to Access (Mobile BLE, NFC)
• Card
• Face Recognition
• Fingerprint
• QR Code
• Apple Wallets

What Happens?

When the user's credentials and permissions are successfully verified:

• The door unlocks for the configured unlock duration.
• The access attempt is recorded as Authorized Access in Access History.
• Any configured notifications or integrations are triggered.
• The event includes details such as the user, access type, door, site, and timestamp.

Access Denied

An Access Denied event is generated whenever a user attempts to access a door but the system cannot authorize the request.

This may occur because the user does not have permission to access the door, the credential is invalid or expired, the access schedule does not allow entry, or another access rule prevents authentication. 

What Happens?

When access is denied:

• The door remains locked.
• The denied attempt is recorded in Access History.
• The event includes the reason for denial whenever available.
• Notifications can be sent if configured.

Door Open

A Door Open event is generated when the door contact sensor detects that the door has been opened. This event confirms that the physical door has transitioned from a closed state to an open state.

Note: This event is available only for doors configured with a door sensor.

What Happens?

• The door status changes to Open.
• The event is recorded in Access History.
• The system begins monitoring how long the door remains open.

Door Closed

A Door Closed event is generated when the door contact sensor detects that the door has been closed. This indicates that the door has returned to its normal closed position.

What Happens?

• The door status changes to Closed.
• The event is recorded in Access History.
• Any active Door Open Too Long condition is cleared.

Door Mode Changed

A Door Mode Changed event is generated whenever the operating mode of a door is modified. Door modes can change automatically or manually depending on system configuration.

Possible Sources

• Schedule
• Cloud (Web Portal)
• Mobile App

What Happens?

• The new door mode is immediately applied.
• The event records the state the door was in and which state it changed to.
• The updated door mode is reflected throughout the system.

Door Open Too Long (DOTL)

A Door Open Too Long (DOTL) event is generated when a door remains open longer than the configured Door Open Too Long timeout. 

This event helps identify doors that have been unintentionally left open or are being held open longer than expected. 

What Happens?

• A Door Open Too Long event is recorded.
• The door alarm is activated.
• Notifications are sent to configured users.
• The alarm continues until the door is closed or the condition is cleared.
• The alarm continues until the door is closed or the condition is cleared.

Door Open Too Long Reset

A Door Open Too Long Reset event is generated after a Door Open Too Long event when the door is closed.

What Happens?

• The Door Open Too Long condition is cleared.
• The alarm stops.
• A reset event is recorded in Access History.

Tamper Alarm

A Tamper Alarm event is generated when the reader or device detects physical tampering. 
Spintly readers include a built-in tamper switch that is pressed when the device is securely mounted during installation. If the device is removed, opened, or loosened, the switch is released and the system detects this as a tamper condition.

What Happens?

• A Tamper Alarm event is recorded.
• The device alarm is activated (if configured).
• Notifications are sent to the configured users.
• The device remains in the tamper state until the condition is reset.

Tamper Reset

A Tamper Reset event indicates that the tamper condition has been successfully cleared.

What Happens?

The tamper condition is cleared only when:

• The tamper switch is pressed back into its normal position.
• A valid Authorized Access is performed.

Once both conditions are met:

• The alarm stops.
• A Tamper Reset event is recorded.
• The device resumes normal operation.

Door Break-In

A Door Break-In event is generated when the door is opened without first receiving a valid authorized access.

This usually indicates a forced entry or unauthorized opening of the door while it is expected to remain locked. Enterprise systems commonly refer to this event as Door Forced Open. 

What Happens?

• A Door Break-In event is recorded.
• The door alarm is activated.
• Notifications are sent to configured users.
• The event remains active until the break-in condition is cleared.

Door Break-In Reset

A Door Break-In Reset event is generated when the break-in condition has been cleared.

What Happens?

The reset event is generated when one of the following occurs:

• Break-In Detection is disabled.
• The door sensor is disabled.
• A valid Authorized Access is performed.

The system then:

• Stops the alarm.
• Clears the break-in condition.
• Records a Door Break-In Reset event.

Fire Alarm

A Fire Alarm event is generated when the controller receives a fire alarm signal from the connected fire alarm system. During a fire alarm, the controller follows the configured emergency behavior to ensure safe evacuation.

What Happens?

• Fire Alarm mode is activated.
• Doors operate according to the configured fire safety settings.
• The event is recorded in Access History.
• Notifications are sent if configured.

Fire Alarm Reset

A Fire Alarm Reset indicates that the fire alarm condition has been cleared and the system has returned to normal operation.

Reset Methods

Local Reset -  When the fire alarm is reset from the controller or fire panel:

• Fire Alarm mode is cleared.
• A Fire Alarm Reset event is recorded in Access History.

Cloud Reset - When the fire alarm is reset from the web application:

• Fire Alarm mode is cleared.
• No Fire Alarm Reset event is recorded in Access History.

Antipassback Events

Anti-Passback events are generated when a user's access attempt is evaluated against the configured Local Anti-Passback policy. These events are recorded in Access History and help administrators monitor violations and access restrictions.

Local Credential Verification Failed

A Local Credential Verification Failed event is generated when the reader or controller cannot verify the user's credential locally while enforcing Anti-Passback.

What Happens?

• Access is denied.
• The event is recorded in Access History with the reason Local Credential Verification Failed.

Local Soft Anti-Passback Events

A Local Soft APB Violation event is generated when a user attempts to re-enter without completing the required entry and exit sequence.

What Happens?

• Access is granted.
• The event is recorded in Access History with the reason Local Soft APB Violation.

Local Hard Anti-Passback Events

A Local Hard APB Violation event is generated when a user attempts to re-enter without completing the required entry and exit sequence.

What Happens?

• Access is denied.
• The event is recorded in Access History with the reason Local Hard APB Violation.
• Access remains restricted until the configured Violation Expiry duration elapses or the violation is cleared.

Local Hard APB Expired- Local Hard APB Expired event is generated when the configured Violation Expiry duration has elapsed after a Local Hard APB violation.

• The user's Anti-Passback state is reset.
• The next access attempt is granted.
• The event is recorded in Access History with the reason Local Hard APB Expired.

Late Access Exemption - Late Access Exemption event is generated when the configured Late Access Exemption duration has elapsed, automatically clearing the user's Anti-Passback state.

• Access is granted.
• The event is recorded in Access History with the reason Late Access Exemption.

Local Timed Anti-Passback Events

A Local Timed APB Violation event is generated when a user attempts to access the same reader before the configured Minimum Wait Time has elapsed.

What Happens?

• Access is denied.
• The event is recorded in Access History with the reason Local Timed APB Violation.

Local Timed APB Expired - A Local Timed APB Expired event is generated when the configured Minimum Wait Time has elapsed.

• The timed restriction is removed.
• The next access attempt is granted.
• The event is recorded in Access History with the reason Local Timed APB Expired.