FAQ: society amenity booking
What is amenity booking on Plinth? A way for residents to reserve time slots for shared facilities (clubhouse, gym, party hall) and for admins to manage availability and approvals.
Who creates amenities? Society admins from Admin → Amenities (/admin/amenities).
Who can book? Active society members from Amenities (/amenities).
What booking statuses exist? Pending, Confirmed, Rejected, Cancelled, Completed, and No show.
How does approval work? When an amenity has requires approval on, new bookings start as
pending. An admin can approve (approve_amenity_booking) or reject with reason
(reject_amenity_booking).
Can residents book any slot? No. Each amenity can enforce minimum notice, max advance window, max duration, and max guest count.
Can two people book the same slot? No — Plinth uses a database exclusion constraint. Overlapping pending or confirmed bookings for the same amenity are rejected with "slot already booked."
Can I cancel my booking? Yes — if you made the booking and it is still before the cancellation cutoff for that amenity. Admins can cancel pending/confirmed bookings at any time.
Can admins delete booking history? No. Admins now close bookings by status transitions (approve/reject/cancel/complete/no-show) instead of deleting records.
What tier is amenity booking on? Community — see pricing.
How is this different from Events? Events are open community gatherings with RSVPs. Amenity booking reserves exclusive use of a facility for a time window.
Is there an audit trail? Yes — book, approve, reject, cancel, and completion transitions are written to the society audit log.