Central reservations
One desk over every hotel in the group: every booking on one screen, and a booking taken into a hotel nobody is standing in — with that hotel's own business date respected.
A group of hotels sells from one phone. The person answering it needs to see what every hotel can sell, book into any of them, and never touch a hotel's day from outside it. The central desk is that person's screen.
Every booking in the group
One list, every hotel the reader may see, filterable by hotel, status, source, date and search — a guest's name, a company, a reference. What was taken last is first, so the nine bookings the channel delivered this morning are at the top and not on page four. Each row says when it was taken, when it last changed and what changed.
Booking into a hotel from outside it
The central desk takes a booking into any hotel in the group with the same quote and the same rules as that hotel's own desk. What it will not do is act on that hotel's day: check-in, the folio and the night audit belong to the hotel and its business date, and the central desk respects the date the hotel is on.
Who may see what
Row-level security decides. A hotel login sees its own hotel; a group login sees the group; a platform user sees nothing until a hotel has let them in. The screen has no filter that could be widened by calling the API directly.