One environment per property, isolated by construction.
PAPERBOAT
It is not a shared system with a filter per client. Every property is instanced with its own data, users, rules, voice address and visual identity — and the isolation is guaranteed in the database, not on the screen.
The PAPERBOAT operations panel. It creates and activates properties, follows the health of each one, sends announcements to the base and receives the tickets from all of them. No screen in here is visible to the client.
Management, trustee, board, gate, concierge and staff. Each profile sees what belongs to it, and what each one may do is decided on the server, not hidden on the screen. The board sees the accounts; the gate does not see the finances.
Owner, resident, tenant and guest. Requests come in through the voice page, the lobby totem or an external link, and land in the queue of the right property. Each one sees only their own unit.
Three layers of defence, each one enough on its own.
The session token carries the property, the profile and the unit. No screen decides what to show on its own.
Every route of the interface demands the matching permission before answering. Hiding the button is not the protection.
The database only returns rows of the property active in the session. A query that forgets the filter comes back empty, not with the neighbour's data.
The owner only reaches their own unit. The rule holds for queries, for bookings and for what the voice assistant answers.
Each property's voice page has its own address and its own context. The assistant knows no other property.
The trail records the origin of every action and is editable by no one — not by the management, not by us.
There is no integration to negotiate and no server to install.
The property is born instanced, with amenities, profiles, suggested rules and its own voice address. It takes minutes.
Units, owners, parking spaces and vehicles come from the spreadsheet you already have. We load it together with your team.
Bylaws and house rules become configuration: notice period, capacity, seasonal limits, fees and what each profile may do.
An invitation by link and a totem in the lobby. From there the operation runs on its own, and support is one ticket away.
High standard does not go with an e-mail queue. The ticket is opened inside the platform, lands in our command tower and carries a deadline agreed in the contract.
Management and the trustee open the ticket from their own screen. The conversation stays in the ticket, with priority, category and deadline visible to both sides.
Recurring questions live in the help inside the product, written in the language of the people who operate it.
On the Resort plan, one person follows the property, reviews usage every quarter and anticipates what will be needed.
Gate, concierge and management trained at rollout and whenever the team changes, at no extra cost.