> ## 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.

# Manage combined tables

> Group at least two physical tables into a reusable booking unit with its own party limit.

A combined table is a virtual booking unit made from at least two physical booking tables. It keeps an ordered member list, an optional room, a name, and a maximum party size.

## Who can do this?

Owners and Managers 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

Open **Settings → Rooms & tables**, then choose **Add combined table** from a room’s overflow menu or the relevant unassigned controls. Existing combined cards provide Edit and Delete.

## Steps

1. Enter a unique name and select a room or no room.
2. Add at least two physical tables as members. Drag members to preserve the intended order.
3. Review the suggested maximum party size, which follows the sum of member seats until you override it.
4. If you enter a custom maximum, use Reset when you want to return to the seat sum.
5. Save and confirm the member names and displayed combined capacity.

## Platform notes

The backend writes the parent and membership rows in one transaction. All members must belong to the same store, and a supplied room must also belong to it. Updating with a member list fully replaces and reorders membership. Deleting the combination removes membership links but does not delete the physical tables.

## Market notes

The model is identical for GB and DE. Combined names and capacity are shop data, not automatically localized. Treat the configured maximum as an operational booking limit, not as legal occupancy guidance.

## Troubleshooting

Save remains unavailable with fewer than two members, an empty name, or a maximum below two. If a member is not listed, confirm it belongs to the same shop and has not already been selected. After deleting a physical table, review affected combinations because membership cascades away.

## Related articles

* [Manage tables](/en/rooms-and-tables/manage-tables)
* [Understand rooms and tables across Tapp](/en/rooms-and-tables/understand-cross-surface-effects)