Sign in at /{locale}/dashboard. The session lasts 12 hours. Every action is checked again on the server against the role of the signed-in account.
Sections
| Section | What you do there |
|---|---|
| Overview | Revenue this month, occupancy this month and for the next 30 days, upcoming bookings, average rating; revenue by month (past and booked ahead); bookings by status; today's arrivals and departures; top stays; where guests come from; open inquiries; latest reviews. Banners link to requests waiting for confirmation and to cancellation requests |
| Calendar | Every stay × every night for 14 to 45 days. Booked nights are coloured by status and show the guest; blocked nights are hatched; free nights show their price. Block dates closes nights for maintenance or the owner's own use; click a block to open it again |
| Bookings | Search by code, guest, email or phone; filter by upcoming or past, status, stay, or "cancel requested". New booking adds a booking taken by phone (confirmed at once, same availability rules) |
| Booking page | Guest, stay, door code, price night by night, timeline of every change, internal note. Buttons move it along: Confirm → Check in → Complete, or Cancel. Mark as paid / refunded. Decide on cancel requests |
| Stays | Cards of every stay with its rate, host and upcoming bookings; destinations list. The stay editor has names and texts in both languages, photos (upload, reorder, cover), amenities, nightly, weekend and cleaning prices, minimum nights, guests and rooms, seasonal prices, host, visibility and "our pick" |
| Inquiries | Questions from the contact form and from stay pages, with dates and guests. Reply by email, keep a team note, mark answered or closed |
| Reviews | Reviews waiting, published and hidden. Publish or hide, and reply (the reply shows under the review on the stay page) |
| AI assistant | Ask about bookings in plain language. See AI features |
| Company settings | Names, tagline, about, contact details, taxes, check-in and check-out times, how far ahead guests can book, free cancellation days, payment switches, "taking online bookings" |
| Admins | Accounts, roles, new passwords, deactivate (takes effect on the next request) |
| Admin roles | The permission table below, as the server applies it |
Status flow
PENDING ──> CONFIRMED ──> CHECKED_IN ──> COMPLETED
│ │
└────────────┴──> CANCELLED
- Check-in is possible from the arrival day, not before.
- A checked-in booking cannot be cancelled, only completed.
- Cancelling frees the nights in the same database transaction.
- Every move is written to the booking's timeline with who did it.
Roles
| Permission | Owner | Admin | Host |
|---|---|---|---|
| Overview, calendar, bookings and guest details | ✓ | ✓ | own stays |
| Block and unblock nights | ✓ | ✓ | own stays |
| Confirm, check in, complete | ✓ | ✓ | own stays |
| Cancel bookings, record payments and refunds, add bookings by hand | ✓ | ✓ | |
| Create and edit stays, photos, prices, seasons, destinations | ✓ | ✓ | view own |
| Inquiries, replies to reviews | ✓ | ✓ | own stays |
| Publish and hide reviews, AI assistant | ✓ | ✓ | |
| Company settings, admins and roles | ✓ |
The table lives in src/lib/roles.ts; both the API and the dashboard menus read it, so a change there applies everywhere. Hosts see only the stays where they are chosen as Host; another stay's booking answers "not found" for them. There is always at least one active owner: the last one cannot be demoted or deactivated.