Most people familiar with ANPR understand the general concept of a whitelist: a camera reads a plate, checks it against a list of authorised vehicles, and opens a gate. In practice, however, much of the added value lies in how those lists can be structured, managed, and automated.
Meet the new CortexConnect cloud portal
CortexConnect expands the ways in which ANPR-based projects can be implemented when combined with an internet-connected AVUTEC ANPR camera. Any changes made within the portal are instantly synced to all connected cameras in real-time, across one or multiple locations.
This article focuses on the whitelist-related functionalities of the portal. In CortexConnect, whitelists can be time-bound, made visible only to specific users based on their role, and triggered by real-world events. Each of these capabilities addresses a real operational problem — and together they add up to more than simple allow/deny lists. The following example scenarios reflect possible configurations within the CortexConnect cloud portal.
Real life scenarios
Scenario 1: Standalone operation: access that works uninterrupted, even during a connection loss
A common concern with cloud-managed access control is what happens when the network goes down. With AVUTEC, the answer is: nothing changes. Whitelists are stored directly on the camera itself — at the edge — so the device can read a plate, check it against its local list, and open the barrier entirely independently of any server or internet connection.
When connectivity is restored, the camera syncs with the cloud platform and picks up any list updates made while it was offline.
Scenario 2: Schedule-based whitelists for pre-defined access windows
Not all access should be permanent, and manually managing the case-by-case differences of recurring schedules is a common source of administrative overhead in access control.
In CortexConnect, a whitelist can be configured with a defined weekly validity window — a start and end time — allowing access to activate and deactivate automatically without any human intervention.
- A staff whitelist can be set to allow entry only during business hours, reverting to denied access in the evenings and weekends without anyone needing to switch it off.
- A recurring delivery window opens for vendors and couriers every weekday morning and closes again automatically.
Scenario 3: Visitor and guest management: temporary access with no manual cleanup
Temporary vehicle access often requires a physical ticket, registering a plate at reception, or calling security to open a barrier — each step introduces friction and depends on someone being available to act.
Temporary whitelist entries with short validity periods solve this cleanly:
- A hotel adds a guest’s plate only for the duration of their stay.
- A kiss-and-ride zone grants a one-hour free access window from the moment a vehicle arrives.
When the period expires, the entry is removed automatically — no reminder needed, no manual revocation.
A particularly useful extension of this is entry-to-exit pairing. When a vehicle enters, the entry camera reads its plate and automatically adds it to a temporary whitelist on the exit camera for a configured time window.
The driver completes their visit and leaves — the exit barrier opens without any additional action required. No ticket, no app, no payment terminal. Once the window expires, the plate is removed.
This eliminates one of the most persistent security gaps in conventional access control: lists that grew over time and were never cleaned up, full of plates belonging to vehicles that are no longer authorized to access the site.
Scenario 4: Staff and resident access: separate lists for separate groups, with one camera
In facilities where distinct groups share the same physical infrastructure — a residential complex with residents and maintenance staff, a business park with several tenants — managing everyone from a single whitelist quickly becomes unworkable.
CortexParking supports syncing multiple whitelists on a single camera, each running independently. A residents’ list, a facilities management list, a retail delivery list — each with its own schedule, its own validity rules, and its own administrator.
For the people using the facility day to day, none of this complexity is visible. Their vehicle is recognised on arrival, the barrier opens, and they drive through.
Scenario 5: VIP notification: turning an access event into a service moment
Access control is usually framed as a security function. But the plate-recognition event that opens a barrier can also trigger a notification, which can be used to improve the experience of the person arriving.
When a plate on a designated VIP list is detected, an automated alert can be sent to reception staff or a meeting host.
- In a corporate environment this means a key client is expected before they reach the front desk — enough time to have someone ready to greet them.
- In a hotel, the front-of-house team can deliver a more personalised arrival experience by being notified of the guest’s arrival before the guest has finished parking.
The same trigger mechanism works in the opposite direction for vehicles that should be flagged. A plate associated with a previous incident or an unauthorised user can generate an immediate alert to a security manager when it appears at any AVUTEC camera on the site — with access denied automatically, and without requiring anyone to be watching a screen.
More than a simple list of license plates
Taken individually, each of these capabilities solves a specific problem. Taken together, they represent a meaningful shift in what a modern ANPR system such as AVUTEC’s can offer.
A well-configured whitelist architecture:
- removes unnecessary manual administration
- closes the security gaps that accumulate over time
- gives different stakeholders appropriate control over their own access groups
- turns routine access events into operational intelligence
None of this requires complex infrastructure. AVUTEC ANPR cameras store and enforce license plate lists locally. The CortexConnect cloud platform manages permissions, distributes updates and applies rules.
The intelligence is in the system; the experience is simply that the gate opens.
