Hotel ID Login and Data Isolation
Staff sign in with a hotel ID, email and password, and database-level row security decides exactly which property's data each login can see.
Your data stays inside your hotel, and the database itself enforces that, not just the screens.
How sign-in works
- Your colleague types your hotel ID.
- Then their email.
- Then their password.
After that, a rule attached to every table settles which rows that login can read or change. Even a careless query cannot reach another property's records.
Nobody gets in by default
- A fresh login can open no property until someone grants one.
- A hotel newly added to your group stays hidden from existing logins until an administrator allows it.
- A test suite checks this by logging in exactly as the app does, and it has already blocked two regressions before release.
If you run several hotels
Your group account holds them all. A group login sees only its assigned properties, the owner sees every one, and the central desk, Hotel CRM and occupancy heatmap show whatever that login is permitted.
Where our support team stands
Our support staff sit outside your account with no view inside. To enter they need your permission, which expires, is recorded and stays visible to you.