Permit categories
Model the resident, employee, contractor and seasonal rights the organization actually offers.
Parking rights
Digital parking permit management
A digital parking permit records who may park, which vehicle or credential identifies them, where the right applies and when it expires. Lexoh organizes issuance, changes, renewal and validation around approved permit categories and the equipment or field process used at the site.
Permit policy
Plates, cards and codes
Zones and periods
Renewal rules
Scope by site
Operating design
A permit is an operating rule, not just a form
Start with the permit policy: eligible users, supporting information, approval responsibilities, authorized zones and validity periods. Then map those rules to the credential and lane configuration. A resident changing vehicles should follow a defined replacement process rather than gaining an unintended additional right. Coordinate parking access control with a separate temporary visitor workflow so long-term and occasional access remain understandable.
Validity periods
Set dates, hours and conditions for each category.
Authorized zones
Limit the right to the locations and lanes that serve its purpose.
Selected identifiers
Link each permit to a plate, card, tag or QR code according to the equipment and users at the lane.
Renewal cycle
Define the states, notices, validations and responsibilities that apply to renewal.
Operational history
Specify the changes and events authorized staff need to review.
Decision path
The life cycle of a managed permit
Approval creates a right, activation connects it to an identifier, and validation checks it at the site. Renewal or replacement must carry forward only the zones and periods that staff have authorized.
- 01QualifyUser, vehicle and need
- 02AssignProduct, zone and period
- 03ActivatePlate, card or code
- 04ValidateRules checked at the site
- 05RenewChange, extend or expire
On site with Lexoh
Rights connected to the site context
An operating view can connect rights with the sites, zones and equipment included in the configuration. The permit then belongs to the approved access workflow rather than an isolated record.
What this changes in the project
Equipment placement, civil work, communications and operating procedures are validated together before commissioning.
Turnkey delivery
Move from a register to an operating system
We help translate current policy into understandable categories, periods, zones and validation methods.
- 01Inventory current permit categories
- 02Clean and prepare import data
- 03Configure zones, calendars and statuses
- 04Attach plates, cards or other credentials
- 05Define renewal and replacement cases
- 06Train administrative and field teams
Operating contexts
Permits shaped around site populations
Residents
Rights by address, unit, vehicle or zone where policy allows.
Employees
Access by schedule, site, shift or category.
Contractors
A limited period and only the zones required for the work.
Seasonal users
Longer rights with a defined renewal cycle.
Before specifications
Rules to clarify before migration
Who approves each permit?
Set roles and supporting information by category.
How many vehicles can be attached?
Clarify substitutions and simultaneous use.
How is the right validated?
Choose a method that fits the barriers, readers or field process.
What happens at expiry?
Plan notices, grace periods, deactivation and renewal.
Questions asked before a project
Clear answers about scope, operation and integration.
That depends on the selected journey. A permit can be associated with a plate or another identifier when that method is supported; a card or tag may still be required for the lane or population.
A temporary category can be configured with a defined period, schedule and set of zones when that function is included in the approved scope.
The selected process identifies a plate, card, tag or QR code and checks the associated right for the current site, zone and period. Equipment-based validation and a staff field check are different workflows. Specify which method is included, who handles an unreadable credential and how permit changes reach the operating team.
A multi-site structure organizes sites, zones and roles within the deployment scope. Define which rights are shared and which remain specific to each site.
A permit establishes permission to park under defined rules. It does not automatically reserve a particular space or guarantee that capacity is available. If the project needs assigned spaces, quotas or another allocation process, document that requirement separately and confirm how the selected system and operating team will manage it.
Prepare the active user or account, credential or plate, permit category, zones and validity dates. Resolve duplicate, expired and incomplete records before import. Test a representative set against the new access rules, then agree on the changeover date and who handles corrections so the old and new permit lists do not conflict.
Verify the permit holder before suspending the lost credential and assigning a replacement. Keep the approved permit period and zones, while deciding explicitly whether any other linked identifiers remain active. Test the replacement using the supported administration process and record who made the change. Issuing another tag without dealing with the missing one can leave an unwanted access right in circulation.
Assign responsibility for the departure notice and the effective end of parking access. Review the person’s active permits and associated plates, cards or tags across the sites they could use. Remove or expire the relevant rights through the supported process, check the resulting status and recover physical credentials where applicable. Keep the departure workflow separate from creating a new occupant’s permissions.
A renewal should confirm that the holder still meets the site’s criteria, that vehicle and contact details remain current and that the next validity period is approved. Decide how unpaid, incomplete or late renewals are handled before the existing right expires. Define who communicates the outcome and verify the supported renewal workflow; extending dates alone does not resolve eligibility or payment questions.
Turn permit policy into a clear process
We can map categories, data, zones and validation methods before configuration begins.