> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand rooms and tables across Tapp

> Understand how table configuration affects bookings, live floor, POS, layout, and guest availability.

Rooms, physical tables, combined units, availability, and layout are shared operational data. A configuration change can affect several Tapp surfaces even though it is made from one Admin settings page.

## Who can do this?

Owners and Managers and Staff can use the described parts. Only Owners and Managers have configuration write access; Staff access remains read-only or operational. API authorization is authoritative.

## Where

Owners and Managers configure data in **Settings → Rooms & tables**. Owners, Managers, and Staff encounter the result in Bookings, Live floor, table sessions, and table-aware POS selection; guests encounter eligible inventory in booking flows.

## Steps

1. A room groups tables, sets allocation priority, and owns a visual floor layout.
2. A physical table contributes seats, minimum/maximum party size, priority, room assignment, and optional placement.
3. A combined table groups physical table IDs into a reusable unit with its own maximum party size.
4. Offline priority excludes a physical table from online allocation but leaves the record available for other controlled workflows.
5. Bookings and active table sessions retain references; review them before moving, combining, hiding, or deleting a table.

## Platform notes

The Admin App and API use stable table IDs across settings and operations. Live-floor and POS views consume room, table, combined membership, and session data; the layout changes visualization, while capacity and priority affect allocation semantics. The API blocks deletion of a table referenced by active future bookings, but configuration changes still require operational coordination.

## Market notes

The data model is shared by GB and DE. Localized labels do not duplicate or translate merchant-entered room/table names. Market differences do not create a separate Germany hierarchy; the same category documents the shared behavior.

## Troubleshooting

When surfaces disagree, first confirm shop and table ID, then refresh settings, bookings, and live-floor data. Check Offline priority, room assignment, combined membership, and active sessions separately. Do not delete and recreate a table to fix a display issue because that changes its identity and can break references.

## Related articles

* [Manage rooms](/en/rooms-and-tables/manage-rooms)
* [Manage tables](/en/rooms-and-tables/manage-tables)
* [Manage combined tables](/en/rooms-and-tables/manage-combined-tables)