Prevent parking abuse via ASE.
This feature's availability depends on your subscription plan and role.
Definition: Access Sequence Enforcement (ASE) is the validation that a user cannot reopen a gate after having already passed through it in the same direction.
What is Access Sequence Enforcement (ASE)?
ASE is the validation that a user cannot reopen a gate after having already passed through it in the same direction. This means that the gate will not open via any access method (app, ANPR, code) if the last gate opening was identified to be in the same direction.
Example: A user enters the parking lot through the IN gate and is parking inside. If they attempt to use the app to open the IN gate again to let someone else in, this will not be possible if ASE is enabled.
What is the purpose of ASE?
ASE prevents abuse of the system by users. Users may book a paid parking spot and try to use one booking for multiple people by opening the gate multiple times during the reservation period. This is no longer possible with ASE.
How do I enable ASE?
ASE must be enabled by your Account Manager. Reach out to them to better understand the implications on your use case and discuss the activation of this feature.
How do I know ASE is enabled and potentially blocking a user?
Both the app and access logs will indicate if a user was refused access due to ASE.
In the access logs, the reason for refusal will be marked as "Access sequence violation":
Users will be informed in the app that the specific access is unavailable because it has already been used for the ongoing reservation.