Time and zone permissions
Use access rules when each group has an approved period and entrance.
Compare parking access controlShared parking
Parking management for shared and mixed-use properties
Shared parking management coordinates access for residents, office tenants, retail customers and visitors using one facility. Lexoh connects the property manager’s approved zones, allocations and time windows to the selected lane equipment and management configuration.
Start with the operation
Make the shared-use agreement operational
Residential, office and retail occupants may arrive at different times, but their schedules can overlap. Translate the property’s approved allocation into rules that staff can explain and the selected system can apply. A forecast of unused spaces is not the same as a confirmed allocation.
| Arrival or user | Policy to define | Design consequence |
|---|---|---|
| Allocated users | Which occupant controls each entitlement? | Record the approving party, zone and validity. |
| Time-based sharing | What happens when schedules overlap? | Define exceptions and the transition between time windows. |
| Common visitors | Which occupant is responsible for the visit? | Associate the temporary right with an approver. |
| Shared entrance | Can the physical lane support all arrival types? | Review queues, credential choices and assistance responsibilities. |
From policy to the lane
Give shared operations one clear decision process
List entitlements before adding technology
Collect the approved allocations and distinguish named spaces from zone access. Include the public or visitor area and any periods when another occupant may use it. Resolve conflicting policies before configuring rights.
Define administration boundaries
Assign a property administrator and define which users, zones and schedules each tenant manages. During the demonstration, follow a tenant administrator through adding a user, changing a permission and reviewing a record. Use those tasks to select the administrative roles for the project.
Test overlaps and handovers
Use a resident arrival, an employee staying late and an event visitor as test cases. Verify which rule wins when time windows meet. Explain how the operator handles a valid credential when the user’s intended space is unavailable.
Lexoh software and physical equipment
Match shared rights to software and lane equipment
Administration and allocation
Define which operator may issue, change or withdraw each group’s rights. Demonstrate that separation in the selected software configuration. The illustrated Security Center device view shows entry events and controls; space allocation and tenant permissions require their own review.
Credentials at the common entrance
Select a presentation method for each group and confirm how the reader passes its result to the controller. A close-range card reader and a reader for vehicle-mounted tags serve different approaches. Test retained credentials before promising that residents, employees and visitors can all use their existing cards.
Barrier, detection and assistance
Review the common lane’s barrier, vehicle detection and assistance point together. Test an arrival during a schedule overlap and a driver whose permitted area is full. Entrance control alone does not locate an empty stall; any occupancy or reservation equipment must be included explicitly.
Planning exampleSee the documented Scotiabank installation →
Residential parking is shared with daytime offices
Consider a mixed-use property proposing daytime use of some residential spaces. Before any scheduling, confirm the allocation policy and which spaces are actually available. Review a resident returning early and an employee leaving late. The access system can apply approved rights, but resolving conflicting entitlements still requires an operating policy. Space sensing or booking, if needed, must be specified separately from entrance control.
Prepare the scope
Prepare a shared-facility operating brief
The approved allocation by occupant, including reserved spaces, common areas and time-based sharing.
Normal schedules, overlap cases, guest approvals and the person responsible for each dispute.
The entrance layout, administration permissions and any separately required booking or occupancy system.
Shared parking questions
Questions to settle before selecting the equipment and configuration.
Define the periods and zones required, then confirm their implementation in the selected configuration. Include holidays, late departures and overlapping schedules in the acceptance tests.
Not always. Some sites use fixed allocations and schedules. If users must book individual spaces, specify that workflow, the booking system and its connection to access rights rather than assuming it is included.
The project can be scoped around a property administrator and designated tenant contacts. Specify which users and records each contact should manage, then review the available permissions in a demonstration. Include adding a user, withdrawing access and checking visibility across tenant accounts.
The number of operators, tenant boundaries, payment rules and entrances influence configuration and testing. Separate any booking integration from access control. Include the work to resolve overlapping rights and train each administrator on the permissions they actually hold.
Have the property manager and each authorized tenant representative confirm the users, zones, time windows and credentials they administer. Resolve duplicate or conflicting allocations before configuring the new system. Test one user from each group, a schedule change and an expired visitor right; agree on who handles exceptions during the changeover.
Lexoh combines cloud management and offline operation. Its mesh network lets site devices communicate without internet, while access depends on powered equipment and locally available permissions. Test each user group at a schedule boundary, then verify that changes reach the affected controllers after reconnection. Offline entry does not resolve conflicting allocations or guarantee that a shared space is available.
Resolve the shared-use rules before configuring access
Send the allocations, schedules and entrance plan so the property’s occupants can review a common operating scope.