The system supports different levels of infractions, configurable per office, and applies progressive blocks based on user recurrence.
Penalty Rules Configuration (ADMIN)
From the administration panel, within the office configuration, administrators can define the penalty rules that will apply to parking reservations.
Infraction Cancellation Time Range (start time / end time)
Allows defining a time range during which, if a user cancels a reservation, an infraction will be generated.
Example:
Start time: 07:00
End time: 09:00
If the user cancels within this range, an infraction is generated.
If the user cancels outside this range, no infraction is generated.
Hide Delete Button on Reservation
This parameter hides the delete reservation button once the configured end time has passed, only for the same day of the reservation.
This prevents users from deleting reservations outside the allowed period.
Maximum Number of First-Level Infractions
Defines how many first-level infractions a user can commit without being penalized.
First-level infractions:
Do not block the user.
Send a notification email informing about the rule violation.
Are recorded in the history.
Once this limit is exceeded, the next infraction automatically becomes a second-level infraction.
Infraction Validity Period
You can configure validity periods (in days) for:
First infraction
Second infraction
Third infraction
These periods define how long an infraction is considered for escalation.
If the user commits another infraction within the validity period, the next level will apply.
Additionally, for second and third infractions, the effective penalty days are configured — these are the days during which the user will not be able to make reservations.
Ignore Infractions
From permission groups and employee types, administrators can enable the option to ignore infractions.
Users with this option enabled:
Do not generate infractions.
Do not receive emails.
Are never penalized, regardless of their behavior.
System Behavior
Cancellations
If the user cancels within the configured time range, an infraction is generated.
If the user cancels outside the range, no infraction is generated.
Check-in
If the user does not perform the check-in for a same-day reservation, an infraction is generated automatically, regardless of the configured time range.
Infraction Escalation
First infraction: email warning, no block.
Second infraction: active penalty according to configured days.
Third infraction: longer penalty according to configuration.
Impact of an Active Penalty
When a user has an active penalty:
They cannot create new parking reservations.
All existing reservations and pre-reservations that fall within the penalty period are automatically deleted.
Manual Penalty Management
In addition to the automatic system, administrators can manually create penalties from:
Users → Penalties
From there they can:
View the complete history.
Change the status of a penalty (active or expired).
Download the history in CSV format.
Remove the penalty.
Creating a Manual Penalty
When creating a manual penalty, it is registered directly as a second-level infraction, without going through the first level.
The following data must be completed:
User
Penalty start date
Expiration date (end of the block)
Validity date (for escalation to third level if the user repeats)
Status (active or expired)
An active manual penalty:
Blocks the user.
Deletes existing reservations within the penalty period.
Escalates to third level if the user reoffends within the validity period.
Feature Scope
Currently, this penalty system applies exclusively to the parking module.
Penalty Examples
Example 1: Cancellation within the infraction range (first infraction)
Configuration:
Infraction range: 07:00 to 09:00
Max first-level infractions: 2
Situation:
A user has a parking reservation for today and cancels it at 08:30.
Result:
A first-level infraction is generated.
The user receives a warning email.
The user is not blocked.
The infraction is recorded in the history.
Example 2: Exceeding the maximum number of first infractions
Configuration:
Max first-level infractions: 2
Second infraction penalty: 3 days
Situation:
The user already has 2 first-level infractions.
They cancel again within the range at 08:00.
Result:
The infraction becomes second-level.
The user is blocked for 3 days.
They cannot create new reservations.
Future reservations within the period are automatically deleted.
Example 3: No check-in
Situation:
The user has a parking reservation for today but does not perform the check-in.
Result:
An infraction is generated automatically.
The configured cancellation time does not matter.
The same escalation logic applies based on their history.
Example 4: Reoffending within the validity period
Configuration:
Second infraction validity: 30 days
Third infraction penalty: 7 days
Situation:
The user has an active second-level infraction.
Within those 30 days, they break the rules again.
Result:
A third-level infraction is generated.
The user is blocked for 7 days.
All reservations within that period are deleted.
Example 5: User with ignore infractions profile
Situation:
An executive repeatedly cancels reservations within the infraction range.
Result:
No infractions are generated.
No emails are sent.
The user is never penalized.
Example 6: Manual penalty
Situation:
An administrator manually creates a penalty due to repeated misuse.
Manual configuration:
Penalty start date: today
Expiration date: in 5 days
Result:
The user is blocked immediately.
Existing reservations within those 5 days are deleted.
The penalty counts as a second-level infraction.