Many properties, one login
Switch between properties without signing out. Each property’s rooms, reservations and folios stay apart; guests are recognised across the chain.
Hotel PMS with an open API
One foundation for your next chapter.
Run one property or a chain under one login, with each property’s data kept apart, guests known across the chain, roles with fine-grained permissions and an open API with signed webhooks.
- 1Connect your properties
- 2Bring the team together
- 3Work from one place
Staff roles and permissions, plus a hotel PMS API
Roles decide who sees and changes what. Scoped API keys and signed webhooks connect your own tools.
Roles that fit the job
A receptionist, a housekeeper, a group manager: each role sees and does only what its work needs.
Open where it matters
Documented APIs for staff, guests and apps, signed webhooks for events as they happen, and an API key per property.
What’s included
Supported today. Where something is still planned, the plan table says so.
- Many properties under one login, with guests shared across the chain
- Roles with fine-grained permissions
- An open API, signed webhooks and API keys
- Plan, invoices and usage in a billing screen
In the plans
| What’s included | Starter | Growth | Enterprise |
|---|---|---|---|
| Properties | Per property | Unlimited | Unlimited |
| Rooms per property | Up to 15 rooms | Unlimited | Unlimited |
| Single sign-on | Not included | Not included | Included |
| API and webhooks | Not included | Included | Included |
Add a property in three moves.
Create it, give people access, connect what it needs.
Create the property
Add rooms, room types and rates; the new property gets its own workspace and business date.
Give people access
Assign roles scoped to the property, and group roles for whoever oversees several.
Connect the tools
Issue an API key, subscribe webhooks for the accounting or channel connector, and read plan and usage on the billing screen.
Who works here
Owner of several properties
Runs many properties under one login, with guests known across the chain and each property’s data kept apart.
Administrator
Gives each person a role with fine-grained permissions and issues or revokes an API key per property.
Developer
Builds on the open API with signed webhooks and the connector SDK.
An illustrative day
Opening a second property
The owner adds the new property. Staff get roles scoped to it while the owner keeps oversight across both. A returning guest from the first property is recognised at the second. Finance reads plan, invoices and usage on the billing screen, and the accounting connector receives events as they happen.
A made-up day to show the flow, not a customer story.
Before you get started
How should we plan access across several properties?
Bring a list of properties and team responsibilities to the demo. Review which people need local access and which need oversight across properties, then confirm the available permission controls for that setup.
Is each property’s data kept apart?
Yes. Every record is scoped to its property, and people see only the properties their role allows, while guests are shared across the chain.
Which plan do we need for several properties?
Starter covers one property with up to 15 rooms. Growth and Enterprise run unlimited properties and rooms; single sign-on, audit export and dedicated onboarding are Enterprise.
Let’s talk about your property
More clarity for your team. More care for your guests.
See how LobbyMind could fit your day, your property and your next chapter.
Book a demo