Monitor and manage accesses
      Back to home
      1. Knowledge Base
      2. Access Control
      3. Monitor and manage accesses

      What is the Access Log and how do I use it?

      Learn how to access, analyse and export access events (gate openings) at your parking lot.

      This feature's availability depends on your subscription plan and role.

      Definition: The Access Log is a table containing all the logs of all received access requests of the gates, which are the events at all available entrances and exits. Log of entry, this log is when the request access has been successful and the gate has been successfully triggered.

      Content

      1. What is the purpose of the access log?
      2. Overview of the access log
      3. Statuses and interpretation of logs
      4. Video overview and examples

      1. What is the purpose of the access log?

      The access log represents the real use of your parking lot. This page lists all the events of openings of the entrance and exit gates of your parking lot over a given period of time. It allows you to analyse the reason for an access refusal. The data of the last 4 months is available. You can export the logs of up to 3 consecutive months at a time.

      Example: If a user books a spot from 8 am to 5 pm, this does not mean that they will enter the parking lot at 8 am and leave it at 5 pm. They may enter at 8:14 am, exit at 12:32 pm, re-enter at 1:25 pm and exit at 4:59 pm. These different time slots represent the actual use of the parking lot by the user. Each gate access will be tracked in the access log. It will show 4 access logs for this user.

      2. Overview of the access log 

      From the parking management interface, select "Access logs" on the left hand side or access it via this link.

      The events of the access log are listed in chronological order to show the latest gate openings. It includes events of up to 4 months. It is possible to download up to three consecutive months at once.

      The log contains 7 columns:

      • Date: Date and time of access attempt
      • Identifiers: Indicates how the person/vehicle was identified by the system
        • Licence plate (+partner): The licence plate was read by the camera (ANPR)
        • Email: The Izix mobile app was used to open the gate
        • Control room: The gate was opened via the control room
        • Empty: A visitor opened the gate via URL
      • Licence plate: Shows all licence plates associated to this profile
      • Beneficiary: In case the profile was identified, the name will be displayed here
      • Gate: Shows the gate in question
      • Status: Shows the decision on the gate opening (opened, denied, failed)
      • Reason: Shows the main reason for a refusal or failure

      It is possible to see more contextual details on the profile and access rights by clicking on the eye icon next to the log entry.

      Consult the details section to better analyse why a user may have been refused access.

      3. Statuses and interpretation of logs

      There are three main statuses (=decision on gate opening) displayed in the logs:

      • Opened: The user was identified and the gate was successfully opened based on existing access rights.
      • Denied: An access attempt was logged, but the access was denied. This may either be due to missing access rights of an existing user or the identifier (e.g. licence plate) is not known. 
      • Failed: A failure prevented the gate from opening. There may be a mechanical issue. Please immediately contact support.

      In case of refusal, the main reason is displayed in the reasons column. The most common reasons for refusal and recommendations for action are:

      • No valid access: The profile exists and was identified. The profile is likely lacking access rights or tried to access outside of the timetable 
        -> Review the acccess rights of this profile
      • Unknown identifiers: The licence plate was read, but is not associated to any existing profile
        -> If a user complains that they could not access the parking and the log matches the time of access, they may have forgotten to add the licence plate to their profile. Review their profile and add the licence plate if applicable.
      • No valid parking booking: The profile exists and was identified. They have booking access and tried to access the parking without a reservation
        -> Review the ongoing reservations for this profile and ask them to make a booking if needed
      • User too far from gate: The profile exists and was identified (via the app), but they are too fare from the gate
        -> Ask the user to get closer to the gate. If they are in front of the gate, see this article for more details
      • Entrance method not allowed: The profile exists and was identified. The access method (ANPR, app, code) used is not configured as part of their access strategy
        -> Review the allowed access methods for the access strategy and inform the user to use the correct one

      4. Video overview and examples

      Always consult the access logs to understand why a profile may have been refused by the system. Compare the reasons with the profile's access rights, assigned licence plates and any existing reservations to validate the decision.