Does HETable include integrations and security controls?

Yes. HETable includes scoped API keys, webhooks, permissions, audit logging, security policy controls, and multi-location visibility for operators that need stronger control over restaurant workflows.

HETable feature overview

Restaurant table-management features for reservations, waitlist, seating, and floor control

HETable covers the full front-of-house table-flow stack: floor-plan versions and publishing, host stand execution, reservations and confirmations, waitlist flow, live wait visibility, self-seat and kiosk experiences, staffing and assignment tools, reporting, and admin-grade controls for security and integrations. That includes a restaurant-owned booking widget link teams can place on their own site while HETable still runs the reservation workflow underneath it.

Browse live restaurant reservations Jump to what the app includes Jump to live-service tools

What the app includes today

Floor plans, versions, and live publishing

Build floor plans, save draft versions, review version history, and publish the layout the host tools should actually run on. This keeps seating decisions tied to the real room instead of a static diagram.

Host stand, reservations, and wait flow

Run reservations, walk-ins, live table state, and queue context from one operating layer. Hosts can manage the floor with a live map, a reservations manager, waitlist tools, and a real-time wait board.

Guest-facing booking and self-seat experiences

Guests can book online using booking rules set by the restaurant through a direct HETable booking widget link, a public HETable location page, or both. They can review or cancel reservations through a confirmation flow and, in supported setups, use self-seat or kiosk experiences driven by live availability and party-size fit.

Kiosk concierge and guest guidance

HETable includes guest concierge surfaces that can answer seating questions, suggest a table, estimate a wait, or move guests into the waitlist when the room is full.

Sections, assignments, and floor-team support

Managers can define sections, import or link the schedule, generate Smart Assign, publish station assignments, and give floor teams a Pocket View for table-state updates from the floor.

Manager controls and reporting

Track staff ratings, roster changes, booking settings, reports, table moves, and cross-location visibility so managers can prep the shift and review outcomes after service.

Integrations, security, and oversight

For operators who need deeper control, HETable includes webhooks, API keys, permissions, audit logging, security policies, and multi-location controls.

For focused proof behind those claims, use the self-seat and kiosk page, the floor-team assignment page, and the engineering overview.

Proof behind the reservation promise

Public booking widget linkEach restaurant can copy a HETable booking link onto its own website or guest communications instead of relying on a marketplace profile.

Public HETable location pageThe same restaurant can also keep a crawlable HETable location page for directory discovery and cleaner reservation handoff.

Guest confirmation pathGuests can review or cancel reservations through tokenized links tied back to the booking record.

Host-side room controlReservations Manager, waitlist tools, and live table state still sit behind the public entry points so the workflow stays room-aware.

That means a restaurant can keep its own booking experience on its own site and still use HETable as the live operating system behind the reservation, waitlist, and seating flow.

How teams use HETable

Set up the room: build the floor plan, manage versions, and publish the live layout for the shift.
Prepare the staff: set sections, import or link the schedule, and generate Smart Assign for server coverage.
Run service: use Host Stand, Reservations, Waitlist, Wait Board, self-seat, or kiosk tools based on the restaurant’s workflow.
Review and control: check reports, table moves, staffing, permissions, audit history, and integrations after the shift.

For a full step-by-step walkthrough, use the How HETable works page. For a rollout-focused view, use the Getting Started page. For a final launch review, use the go-live checklist.

What teams actually open during service

These are not placeholder feature claims. They reflect the real product surfaces inside the app today and the buyer language those screens support.

Floor Plan Builder + VersionsCreate layouts, manage version history, and publish the live room before service.

Host Stand + ReservationsRun live floor status, arrivals, reservation edits, and seating decisions from one operating layer.

Waitlist + Wait BoardTrack queue pressure, quoted waits, recent seatings, and live wait conditions.

Self-Seat + Guest KioskOffer guest-driven seating flows with party-size checks, table suggestions, and waitlist fallback.

Guest Concierge ChatGuide guests around seating questions, likely waits, and next-step actions when the room is full.

Sections + Smart AssignBuild sections, import or link the roster, and generate station-ready server assignments.

Station Assignments + Pocket ViewPublish station maps, share printable assignments, and let floor teams update table states from the floor.

API Keys + Webhooks + Audit + SecuritySupport external workflows, tighter permission control, activity review, and policy enforcement for larger operators.

Floor Plan Builder Versions Host Stand Reservations Wait Board Self-Seat Guest Kiosk Concierge Chat Smart Assign Station Assignments Pocket View Reports API Keys Webhooks Audit Log Security Policies

Self-seat and kiosk proof, floor-team assignment proof, and the engineering overview keep the broad feature story tied to live public pages.

How the product is used by role

ManagerBuild and publish the room, configure booking rules, set sections, review reports, control permissions, and monitor multi-location operations.

HostSeat the floor, manage reservations, quote waits, move parties, monitor the board, and hand guests into kiosk or self-seat flows when needed.

Server / Floor TeamUse Pocket View and station assignments to stay aligned with section coverage and keep table-state changes visible from the floor.

GuestBook from the restaurant’s own HETable widget link or public location page, confirm or cancel a reservation, self-seat where enabled, or use the kiosk and concierge surfaces when arriving on site.

Integrations, security, and multi-location control

A large part of the real product is operational control around the workflow, not just the front-door UI. That is especially important when updating parent-site copy or selling to groups.

Scoped API keys for floor data, staffing, reports, ratings, and admin workflows.
Webhooks for staffing, ratings, shift assignments, and table-status event handoff.
Permissions + overrides for tighter role and user-level control.
Audit log for reviewing admin activity across sensitive settings.
Security policies for idle timeout, IP allowlist, and brute-force lockout rules.
Locations dashboard for operators managing more than one restaurant.

See the dedicated integrations and security overview.

Direct answers

What features does HETable include today?

HETable includes floor-plan publishing, host stand controls, reservations, waitlist tools, live wait visibility, self-seat options, guest concierge experiences, staffing workflows, and admin controls like webhooks, API keys, permissions, audit logging, and security policies.

How do teams use HETable during a shift?

Teams usually start by publishing the right floor plan, setting sections and assignments, and confirming booking rules. During service they use the host stand, reservation tools, waitlist, wait board, kiosk, or self-seat experiences as needed. Managers then review reports, staffing, and admin controls after service.

How does HETable fit into the HospiEdge platform?

HETable is the table-management product in the HospiEdge platform. It runs guest flow at the front door and across the floor, then connects outward to scheduling and operations products for labor planning and broader restaurant execution.

Explore focused pages

Restaurant host stand softwareHost workflows, reservations, wait board, and live service control. Restaurant floor plan softwareVersions, publishing, tables, and section-aware layouts. Restaurant seating softwareRotation, self-seat, kiosk guidance, and pacing support. Restaurant self-seat and kiosk softwareGuest-driven seating, kiosk flow, and concierge support. Restaurant floor team assignment softwareSections, Smart Assign, station maps, and Pocket View. Restaurant waitlist softwareQueue flow, live wait visibility, and guest notifications. Restaurant reservation and waitlist softwarePublic booking, host reservation control, and unified arrival flow. Restaurant reservation management softwareBooking settings, reservation edits, confirmations, and arrival handling. Restaurant integrations and security softwareAPI keys, webhooks, audit visibility, permissions, and multi-location control. Restaurant reporting softwareShift summaries, audit visibility, booking oversight, and multi-location review. Restaurant front-of-house workflow softwareSee how managers, hosts, servers, and guests use HETable together. Restaurant multi-location operations softwareLocations dashboard, reporting, audit, and group-level oversight. How HETable worksSee setup, pre-shift, live-service, and post-shift workflows. Browse live restaurant reservationsOpen the public HETable reservation directory with crawlable restaurant pages and direct booking paths. Getting started with HETableSee the practical launch order for setup, shift prep, service, and review. What teams open in HETableSee the real screens managers, hosts, floor teams, and guests use. HETable go-live checklistUse the final launch-readiness review before the first live shift. HETable engineering overviewGive technical reviewers a clean summary of scope, controls, and integrations.

Parent platform links

HospiEdge is the parent platform and HETable is its table-management product destination.

Use HETable for guest flow and floor execution, connect to restaurant scheduling software for labor planning, connect to restaurant operations software for broader execution workflows, and use the new integrations/security page when parent-site buyers need clearer admin detail.