The platform Live

Roles and capabilities

Front desk, housekeeping, back office, manager, administrator — and under each role a catalogue of capabilities that reach down to the button, gated by the module the account has bought.

A role is a starting point, not a wall. Under each role sits a catalogue of capabilities — post a charge, void one, give a discount up to a ceiling, name a rate, pass a room, assign a room, change a vendor's bank, run the audit — and an administrator turns them on and off per login.

Where it is enforced

In the database. A route that forgets to check is still refused by the function it calls, because the function asks the same catalogue. The refusal is a sentence: "Only a supervisor may say a room is ready."

Gated by the module

A capability belongs to a module. A login in an account that has not bought housekeeping has no housekeeping capabilities to be given; the menu does not show the screen; the API refuses the route. A subscription is a fact the catalogue reads.

Team and access

Logins, roles, which hotels, and what each may do — on one screen for the account administrator, with an invitation flow that sets no password on our side.

More on The platform

One database, not five that talk to each otherEvery integration between two systems is a place where a guest becomes two guests and a bill becomes two bills. The way not to have that problem is not to have two systems. The hotel ID, and who may see whatSign-in is a hotel ID, an email and a password; row-level security in the database decides what that login may see; a platform user sees nothing until a hotel has let them in. A group of hotelsOne hotel or twenty, on one account: each with its own business date, rates and rooms; the group with one guest list, one central desk, one heatmap and one set of consolidated numbers. Support access is granted, time-boxed and loggedOur own people cannot open a customer's hotel. The account lets them in for a window, the session is logged, and the account can see afterwards who was inside and when. The manual ships with every screenA hundred and twenty-four pages, written for the person at the desk, filtered by module and role, opened with one key on any screen — and published free at pms.theorionhotels.com/help. When the system refusesEvery refusal is a sentence written for the person at the desk, in the manual, findable by pasting it in — and the rule for what gets refused is one line. The log is the priceEvery change to every record carries who, when, from which login, which address and which machine — and the log is read on one page, by support and by the hotel. Opening a hotelThe wizard takes the code, the GSTIN, the room types with real room numbers and a rate each; readiness says what is still missing; the board tracks it to open — and the hotel opens itself. Modules and the subscriptionEach module is licensed on its own, switched per account by the platform, and the switch has teeth — a suspended account cannot sign in. EmailConfirmations, invoices, payment links, the morning sheet, scheduled reports — sent in the hotel's name, replies routed to a person, every send on the log. SecurityRow-level security in the database, credentials in an encrypted vault, host-only sessions per door, SSH guarded by fail2ban, backups before every migration, and a test suite that signs in as the application role.