Coordinate people & guests
Several hotels, one login
Switch property from the header. Staff see only the one they work at.
The second property is where small-hotel software usually breaks. Either you get a second account and a second password and two sets of numbers that never add up, or you get an enterprise tier priced for a chain.
Neither is right for someone running two resorts in the same town.
Multi-property is one of the modules included in the MangoHost platform — every plan has all of them, so nothing on this page is an upsell.
The workflow
How it works
One account, one login
Properties sit under one account. A switcher in the header changes which one you are looking at, and everything — bookings, staff, stock, analytics — follows.
Adding a property is a dialog, not a sales conversation.
Data that stays separate
Every row of business data carries its property, and every query is scoped to the one you are in. There is no view that quietly blends two hotels' occupancy into one number, because that number would be meaningless.
Staff who only see their own
Access is granted per property. A housekeeping supervisor at one resort does not appear at the other, and does not see its numbers.
You, as the account owner, are the only person moving between them.
Billed per hotel, honestly
Each property is on its own plan, sized to its own room count. A twelve-room inn and a forty-room resort are not charged the same, and neither is charged an enterprise premium for the privilege of being in the same account.
Analytics stay per property, deliberately
There is no combined occupancy figure across two hotels, because there is no honest one. A twelve-room inn at ninety per cent and a forty-room resort at fifty do not average into anything a decision can be made on.
Each property has its own occupancy, ADR, RevPAR and net profit, and you compare them by switching. If you want a group total, the PDF exports are per property and add up cleanly.
Add-ons where they apply
The Restaurant add-on belongs to the property with a kitchen. The Guest Guide belongs to the properties you want it on. Neither is an account-wide purchase, so a resort with a restaurant does not make you pay for one at the inn that has none.
One person moves between them
Staff access is granted per property, and a role at one hotel does not exist at the other. In practice the account owner is the only person who ever uses the switcher — which is exactly the intent.
Every query is scoped to the property you are in, so switching is not a filter applied on top of shared data. It is different data.
In detail
| Several properties per account | Added from Settings. |
|---|---|
| Header switcher | Change property without logging out. |
| Isolated data | Every query scoped to the active property. |
| Per-property staff access | Roles and users granted per hotel. |
| Per-property billing | Each on its own plan and room band. |
| Per-property add-ons | Restaurant or Guest Guide enabled only where needed. |
Who this is for
You run two or three properties
One login, separate numbers, separate staff — and no enterprise tier to buy your way into.
You are about to open a second
Adding it is a dialog. Nothing about your first property changes.
See it on your own property
Thirty minutes with the IslandLink team, your rooms and your rates. No card, nothing to sign.