Overview
Last updated: November 5, 2026
Overview
Welcome to Placeful — a multi-tenant platform for managing events, seats, time windows and bookings with Stripe payments, an embeddable booking widget and role-based access for company teams.
What you can do
- Companies are the tenant. Each company owns events, event types, areas, seats, times and bookings. Users join one or more companies with a role:
owner,admin,manager,member. - Events have a date (optionally multi-day), an optional booking window and capacity. Bookings are made against events — unless the company runs in areas booking model, where customers book an area directly for a time window (an events company can also allow both — see Area booking).
- Venue map & tables — staff draw areas and place physical tables on a visual floor plan (
/venue/map); any booking can be pinned to tables — even spanning several — from the seating map (/venue/seating), the booking editor or the planner. - Closures — rules (date ranges, weekday recurrences, time slices) that block the venue, an area or a table (
/availability/calendar). - Planner — a month grid at
/admin/plannerpainting closures, bookings, events and table moves per day. - Bookings reserve capacity (seats or time slots) and move through a state machine:
Pending→Free/Paid/Added(the confirmed states) →Cancelled,Failed,Expired, or the refund chainRefundPending→Refunding→Refunded/RefundFailed. A submitted promo code parks the booking inPromoPendinguntil staff approves or rejects it. - Widget is an embeddable booking calendar (iframe + script snippet) generated per company for external sites.
- Stripe powers checkout, per-company connected accounts (payouts plus platform application fees), refunds and subscription billing for packages.
- Waitlist — on events with
waitlist_enabled, sold-out customers can queue and are promoted FIFO when a spot frees up. - Ordering — menus with categories, modifiers, courses and optional stock counts; live order tabs on the staff pad, a kitchen board with course firing and prep-time pacing, guest QR self-ordering, printable receipts and a daily cash drawer with Z-report close-out (
/orders). - Staff — employees with roster, contracts, shift schedules, tasks, clock-in timesheets, time-off and payroll summaries; a self-service staff portal and walkie-talkie-style voice radio rooms for the floor.
- Member app — an installable PWA at
/m: today's bookings, the seating map, self-ordering, the kitchen board and push notifications. - Google Calendar — staff can mirror confirmed bookings to their own calendar and see busy-block conflicts.
- AI assistant — an in-app assistant (sparkle button, or Ctrl+K → Ask the assistant in the command palette) answers questions from your company's data and these docs, proposes confirmable changes and navigates to records for you — see AI assistant.
Roles at a glance
| Role | Sees | Can do |
|---|---|---|
| Owner | Everything in their company | Full control: billing, members, stripe accounts, delete company |
| Admin | Operational resources | Manage events, bookings (incl. refunds), members — no billing, no company create/delete |
| Manager | Daily operations | Create/edit events, event types, seats, times, bookings — no areas, no refunds, no member management |
| Member | Own context | View, create and edit their own bookings |
| Employee | Floor surfaces + own portal | Order pad and kitchen board, booking service marks (seated/completed/no-show), voice radio, own schedule/time-clock/time-off — no booking or money management |
Developers (platform staff with the developer flag) bypass all role checks.
Where to go next
- Make your first booking
- Staff docs (Create an event, Pricing, Embed the widget, …) appear in the hub automatically once your role allows them.