Four surfaces. One record.
Every party in a shared property gets its own surface: the owner sets policy, tenant companies run their day, employees book and pass, and enforcement reviews the exceptions. Every administrative change, on any surface, lands in the same audit record. Illustrative data throughout.
Rules are set once and hold everywhere.
Property admins grant stalls to each tenant company, zone by zone, and mark stalls by what they offer: EV charger, oversized, accessible, visitor. Portfolio admins work across their buildings from one place.
Every booking runs the same checks in the same order, and the first one that fails gives the answer, so "why was this refused" always has one. The booking keeps which checks passed and a fingerprint of the policies that applied.
Tenant companies run their day inside the boundaries.
A tenant admin manages allocations, people, vehicles, and disputes, and sees only their own. The isolation is structural, enforced in the database layer; other tenants' rows do not exist in their view.
A shared allocation can be rationed between its groups: each admitted group carries a booking quota (so many bookings per day, week, or month), enforced at booking time, not on the honour system.
Visitor permits are issued by the tenant and carry a QR pass that reception can verify; at the gate, the camera recognises the visitor's plate.
SSO (OIDC and SAML) and SCIM people sync keep the roster current: the tenant's HR reality is the platform's reality.
Your spot, your booking, your pass.
Employees book on an interactive map of the property: one-time or standing bookings, and a waiting list that offers a freed stall to the next person automatically.
On the day, the app is one screen: today's booking and a QR pass for reception. At the gate, the camera recognises the booked plate.
The one word an employee never sees in Vadoris is "governance."
Cameras surface signal. People decide.
ANPR cameras at the entry and exit lanes, integrated through a vendor-adapter layer, match real arrivals against bookings, and flag what does not line up: an overstaying vehicle, a booking never used, a plate with no booking at all.
Tenant admins report what cameras cannot see: a vehicle in a stall allocated to someone else. Vadoris identifies it across tenant boundaries under recorded elevated access and routes the case to the right admin. The reporter learns only "resolved" or "not found", never which company matched.
Either way, the flag carries its evidence to a human reviewer. The system does not fine anyone automatically.
Who can do what is itself a rule.
Authority in Vadoris is a ladder of boundaries. Portfolio admins work across their properties. Property admins run their property: its zones, its stalls and the grant to each tenant. Tenant admins operate inside that grant. Employees book and pass. Each layer works inside the boundary the layer above drew, and cannot see past it. Where one company owns and occupies the building, it holds the property seat and the tenant seat at once; the ladder is the same.
Inside its boundary, each tenant company shapes its own operation: its people, its vehicle roster, its visitor flow, and its own colours and logo on the app its employees see.
Companies with locations at several properties get corporate administrators: authority derived live from the database, bounded on scope and expiry, and recorded whenever it is used.
Every property runs on a written policy.
Booking policies are written down, not remembered. Each tenant company writes its own (who may book which days, for how long, how far ahead, and on which dates nobody may), inside the stalls the building granted it. The most specific policy wins and a deny beats an allow, and a policy simulator tries a booking against the current set before anyone relies on it.
Most properties still run allocation from the lease annex and memory. A written policy can be read, argued with and reproduced.
policies + request → stall B-14 · fingerprint kept with the bookingThe unglamorous parts, included.
Across buildings
- Multi-property portfolios
- One platform across properties: rules per property, a portfolio-level view above them.
- Corporate groups
- A company with locations at several properties is managed as one group, with corporate administrators whose authority is bounded on scope and expiry and recorded when used. Each legal entity remains its own data controller.
- Owner-operated buildings
- One legal entity as both landlord and tenant, with the same rules, boundaries and record.
Connected to what you run
- SSO and SCIM
- OIDC and SAML sign-in; SCIM people sync keeps the roster matched to the tenant's HR systems.
- Analytics access
- Power BI, Tableau and other BI tools connect read-only to a governed dataset; what a connection can read is set by its scope and enforced at the database.
- Vadoris Assistant for Microsoft Teams
- Installed as a custom app by the client's Teams administrator: employees see bookings, check availability, book and cancel, and manage their waitlist place in a private chat, in English.
Run and reported
- Guided onboarding
- A guided sequence for setting up properties and tenant companies, and step-by-step single sign-on connections, run with us in the room.
- White-label
- Tenant-level colours and logo, so the app employees see carries their company's face.
- Price lists and statements
- Price lists per property, zone, tenant, or tenant and zone. Monthly statements are built from bookings and the price list in force and export as PDF, Romanian e-invoice XML, CSV, Excel or JSON; data exports and outgoing webhooks feed your own systems.
- Signed audit exports
- Any selection of the audit log, exported as a signed package with a stand-alone verifier, checkable offline.
See your rules run on your building.
Demos are configured white-glove around how your car park is shared: your companies, your groups, your zones.
Request a demo by emailWrite to hello@vadoris.eu with the property, roughly how many companies and stalls share the car park, and what runs at the gate today. A person replies within two working days.