Reference · built on requestOperator by FibricProperty & tenants

Amenity Booking

Amenity reservations checked against who badged in and what cleaning is due, with a release, a reschedule, or a block proposed.

Request accessPricing ↗

About

A gym, a rooftop, a party room. Each has a booking list, a door, and a cleaning schedule, and they rarely agree. Amenity Booking reads them together. It reads reservations from Entrata getAmenityReservations, or the access groups and schedules you keep in ButterflyMX. It reads access events at the amenity door from Brivo Access, Kisi, Verkada, or Avigilon Alta, and the preventive maintenance and cleaning tasks in Limble CMMS, MaintainX, or UpKeep.

It proposes the fix for each mismatch: release a booking nobody used, move one that collides with a cleaning task, or block the space while a work order is open. You approve each one. It never changes a door state on its own.

This is a reference listing. It documents what Fibric would read from Amenity Booking and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Amenity reservations through Entrata getAmenityReservations, with the unit, the space, and the booked window
  • Access groups, access points, and their schedules in ButterflyMX, where residents get time-limited access to parts of the property
  • Access events at the amenity door: Brivo /events/access by access point, Kisi lock.opened and lock.held_open, Verkada access events, or Avigilon Alta activity events
  • Occupancy: Kisi place.occupancy_rate_limit_reach events, Verkada occupancy trends, or zone counts from Camera Vision on the space
  • Preventive maintenance and cleaning tasks with their scheduled windows in Limble CMMS, MaintainX maintenance plans, or UpKeep preventive maintenance schedules
  • Open work orders on the amenity in the same CMMS, so a space under repair is not offered

Proposed actions

  • Target capability: propose releasing a reservation when no credential was used at the door during the booked window, with a message to the resident
  • Target capability: propose moving the cleaning task, through a Limble task due-time change or a MaintainX work order update, when it overlaps a booking
  • Target capability: propose blocking the amenity while a work order is open, through a Brivo schedule state change or an Avigilon Alta timed entry state
  • Target capability: propose adding the booking resident to the amenity access group for the window, through ButterflyMX, Brivo, or Verkada group membership
  • Target capability: propose a cleaning work order after a heavy-use booking, through MaintainX POST /workorders or Limble POST /v2/tasks

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Release the bookings nobody showed up for

    Entrata lists a party-room reservation. Brivo shows no access event at that door during the window. The operator proposes releasing the slot and a message to the resident, for your approval.

    With Entrata, Brivo Access

  • Move cleaning out of a booked window

    A Limble preventive maintenance task on the pool deck overlaps a reservation. The operator proposes shifting the task's due time, and shows the alternative if you would rather move the booking.

    With Limble CMMS, Entrata

  • Block a space with an open work order

    MaintainX has an open work order on the sauna heater. The operator proposes an Avigilon Alta timed entry state that closes the door until the order completes, and the revert.

    With MaintainX, Avigilon Alta

  • Grant the door for the hour that was booked

    A resident books the rooftop. The operator proposes adding them to the rooftop access group in ButterflyMX for that window, and removing them after it, both as one approval.

    With ButterflyMX

Requirements

  • A source of reservations: Entrata amenity reservations, or ButterflyMX access groups and schedules used as the booking record
  • An access control connector on the amenity doors: Brivo Access, Kisi, Verkada, Avigilon Alta, or ButterflyMX
  • A CMMS holding the cleaning and preventive maintenance schedule: Limble CMMS, MaintainX, or UpKeep
  • Your booking rules: the no-show grace, the cleaning buffer after each use, and which spaces only a person may close
Authentication
It reads reservations, door events, and tasks through the property, access, and maintenance connectors you attach, each scoped as you grant; it holds no keys or logins of its own.

Limits

  • Bookings kept on paper or in an app with no interface are invisible to it. It sees the door, not the list.
  • A door event shows a credential, not a headcount. Occupancy is read only where a sensor or camera zone reports it.
  • It never opens, locks, or blocks a door on its own. A schedule or entry state changes only after you approve, with the revert attached.
  • It charges no fees and refunds no deposits. Money stays in your property system.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Amenity Booking ↗

Questions and answers

What do I sign off on for an amenity?
The release, the reschedule, or the block, one at a time. Each proposal shows the reservation, the door events or occupancy it read, the task or work order it collided with, and the exact change to the schedule or access group. You approve, edit, or dismiss.
What trail does a change leave?
A receipt: the reservation id, the access events cited, the task or work order id, the schedule or group change made, its revert, who approved it, and the message sent to the resident, if any.
Could it lock residents out of an amenity by mistake?
Not on its own. A block is a proposal, with the revert attached, and it applies only after a person approves. Door hardware and standing schedules stay under your access system's control.
Ask about Amenity Booking

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy