One owner. Many properties. One source of truth.
Run a group like a group — not like five disconnected hotels.
Operra's hierarchy goes Owner → Business Unit → Property → Outlet → Employee. Each layer has the right view, the right permissions and the right audit trail. The owner sees consolidated revenue across the group; the front-desk agent only sees their own property.
Built for the hotel groups that outgrew their spreadsheets — and the single hotels that plan to.
The story
From three Excel files to one dashboard.
A family group runs three lodges in northern Tanzania. Each one had its own PMS, its own accountant, its own reporting cycle. The owner waited until the 10th of the month to get a picture of how the group had performed.
Operra was rolled out across all three. Same role definitions. Same audit standards. Same PDF branding. Each property continues to operate independently — including offline — but the owner now opens one dashboard and sees occupancy, ADR, RevPAR and AR for the group, by property, by segment.
The accountant closes the month in 2 days instead of 9.
What it gives you
Built for how operators actually work.
True hierarchy
Owner, Business Unit, Property, Outlet, Employee — each with their own dashboard, permissions and reports.
Consolidated reporting
Group-level KPIs that roll up from real transactions — not exported spreadsheets stitched together at month-end.
Per-property isolation
Each property has its own folios, stock, staff and offline state. One property's outage doesn't touch any other.
Cross-property staff
Move a manager between properties without recreating their user. Roles travel; access is scoped per assignment.
Shared corporate AR
A corporate client can book across multiple properties. One credit limit, one statement, properly attributed per stay.
Per-property branding
Each property keeps its own logo, colours and PDF templates while the back office reports as one group.
By the numbers
Built to scale with you.
Properties supported
Month-end close time
Per-property uptime
Onboarding per property
Security across the group
Row-level isolation, not policy theatre.
Property data is isolated at the database layer via row-level security policies tied to a separate user_roles table. A staff member at Property A literally cannot read Property B's folios — even through the API. Audit logs span the group, scoped to the owner.
Compared to the alternative
What changes when you switch.
Capability
Single sign-on across properties
One PMS per property
Operra
Capability
Consolidated group dashboard
One PMS per property
Operra
Capability
Per-property data isolation
One PMS per property
Operra
Capability
Role definitions reused across properties
One PMS per property
Operra
Capability
Per-property branding on PDFs
One PMS per property
Operra
Capability
Cross-property corporate AR
One PMS per property
Operra
Capability
Independent offline operation
One PMS per property
Operra
Capability
Auditor view across the group
One PMS per property
Operra
The hard questions
What operators ask before they switch.
“Each property stays its own hotel. The group finally feels like one company.”