See the portfolio centrally without flattening each property.
Connect hotels and accommodation locations under one subscriber account while preserving property-level access, branding, operating records and enabled modules.
- Web-based
- Role-aware
- Property-specific
Managing a multi-property group comes with its own operational challenges.
A group needs common oversight and local accountability at the same time. Central access should not erase each property’s inventory, brand or operating reality.
Fragmented property views
Leaders cannot compare operating standing when every location uses a separate record.
Over-broad access
Central tools must not give every user unrestricted visibility into every property.
Different operating models
A hotel, hostel and villa portfolio cannot rely on identical vocabulary or workflows.
Inconsistent controls
Roles, modules and records need governance without removing local responsibility.
Property identity
Each location may require its own brand, content and approved domain.
Central governance with property-aware operation.
PMS connects properties under one account, then uses property permissions, roles, modules and presentation settings to preserve the right boundaries.
Build the portfolio structure
Represent properties and branches inside the subscriber account.
Separate local access
Give people only the properties and responsibilities they manage.
Keep operating models distinct
Use the appropriate inventory and vocabulary for each property type.
Retain local brands
Manage property-specific branding and guest-facing content where included.
The PMS modules that matter to this operation.
Available modules depend on the selected plan and the capabilities enabled for the property.
Property portfolio
Organise multiple properties under one subscriber account.
Property access
Control which locations each team member can open.
Roles & permissions
Match actions to central and local responsibilities.
Property operations
Keep each location’s reservations, rooms and daily work separate.
My Day
Show role-aware priorities in the relevant property context.
Reports
Review operating records within the user’s authorised scope.
Branding & content
Keep property identity and landing content location-specific.
Subscription & add-ons
Manage allowed properties and modules through the account plan.
Follow the work from the first request to the retained record.
Each step keeps its property, guest and account context as responsibility moves through the operation.
- 01Create subscriberEstablish the group account and owner.→
- 02Add propertiesConfigure each location and property type.→
- 03Assign local teamsGrant property and responsibility access.→
- 04Operate locallyKeep daily records inside the correct property.→
- 05Review centrallyOpen authorised portfolio and property views.→
- 06Adjust access or modulesChange entitlements through controlled account actions.→
- 07Grow the portfolioAdd properties when the subscription allowance supports them.
Give each person the property context their responsibility requires.
Role-based access limits pages and actions to the responsibilities and properties assigned to each authorised user.
Group owner
Subscriber, property and subscription authority.
Regional / portfolio manager
Authorised cross-property operating oversight.
Property manager
Local rooms, guests, teams and daily decisions.
Department teams
Property-specific operational responsibility.
Group accounts
Authorised financial and invoice views.
Content / brand manager
Property identity and landing content where assigned.
Anything not granted stays unavailable.

Move from portfolio standing to the exact property record.
Illustrative group views summarise authorised property context and keep every drill-down tied to the correct location.
What changes when the property record is connected.
These gains describe clearer property work—not guaranteed financial or performance results.
Central visibility without shared chaos
Review the group while retaining property-level records.
Safer access boundaries
Limit users by responsibility and property.
Consistent operating governance
Use common roles and controls where they make sense.
Property-specific configuration
Keep inventory, modules and vocabulary appropriate to each location.
Scalable subscription control
Add property or module allowance through the available upgrade flow.
Independent property presentation
Retain local brand, content and approved domains.
One PMS. Configured around your property.
Use one dependable operating base, then shape property structure, access, modules and presentation around the business.
Property-aware setup
Structure PMS around the property, units and operating model.
Role-based access
Give team members access according to their responsibilities.
Modular capabilities
Enable the services relevant to the property and selected plan.
Brand & digital presence
Support the property’s own presentation and guest-facing touchpoints where applicable.
Scalable architecture
Start with the required property and module allowance, then use available upgrades as the operation grows.
Multi-Property Groups PMS questions, answered.
Straight answers about how this property model fits the PMS operating base.
Can one subscriber account contain multiple properties?
Yes. The number of properties depends on the current plan and any active property add-ons.
Can a manager access only selected properties?
Yes. Property access can be granted per user alongside role permissions.
Can different property types share one account?
Yes. Each property can retain its own type, inventory vocabulary and configuration within the group.
Can each property keep its own branding?
Yes. Property branding, landing content and approved domain settings remain property-specific where included.
Can the group add more properties later?
Yes. Available property add-ons and subscription upgrades can increase the account allowance.
Does central reporting expose every property to every user?
No. Views must respect the user’s platform role and granted property scope.
Can modules differ between properties?
Account entitlements set the available modules; property and role configuration determine how authorised teams use them.
Ready to connect your property portfolio?
Discuss the group structure, property types and access boundaries your operation needs.
→