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

# Extend a table session

> Move an active session's expected end safely without running past the next booking on its tables.

Extending changes the operational expected end of an active session. The API clamps the result to the earliest upcoming booking on any occupied table so the extension cannot overrun that reservation.

## Who can do this?

**Owners, Managers, and Staff** may operate Live Floor and table sessions. Room, table, and booking configuration remains Owner/Manager-only wherever its API requires that role.

## Where to do it

In the Management web app, open **Rooms and tables → Live Floor**. Select a table for its card or session. The Management mobile app provides the same core floor, filter, map, table-action, extension, and session-detail areas.

## Steps

1. Open the occupied table's session panel and find **Extend time**.
2. Increase or decrease the added minutes until the preview shows the intended new end. Submit only a positive extension.
3. Read the preview for whether the requested end is free or reaches an upcoming booking boundary.
4. Apply the extension and wait for the success message. The documented Management action extends the session clock; it does not automatically promise a longer linked booking record.
5. Reopen or refresh the table and verify the stored expected end and the next booking context.

## Platform notes

Web and mobile use the same session endpoints. POS orders are anchored through the session ID. Guest bookings from the guest app can appear as incoming floor bookings, but guests cannot operate Live Floor or sessions.

## Market notes

The flow is the same in GB and Germany. Live Floor sends a local time reference for the store; bookings and sessions are shown in that local operating time. Currency differences affect orders, not occupancy logic.

This reflects the product on 17 July 2026. The active session is authoritative: an elapsed booking window does not end physical occupancy, and only a successful session action changes the table state.

## Troubleshooting

* Only an active session can be extended. A closed or missing session returns an error.
* If the stored end is earlier than requested, the server may have clamped it to the next booking. Do not treat that as free time beyond the displayed boundary.

## Related articles

* [View a table session](/en/live-floor/view-table-session)
* [Free a table or close its session](/en/live-floor/free-table-or-close-session)