How property sets can be applied
Property sets can support several organizational and technical scenarios.
Group properties into operational data sets
You can use a property set to group properties and their associated data. For example, a property set can represent a portfolio, region, campus, or other operational domain.
Advantages
• Users can work with a clearly defined collection of properties.
• The selected property set determines which properties are displayed.
• Access to the property set can be assigned to authorized user groups.
Disadvantages
• Users who work across multiple portfolios may need access to and switch between multiple property sets.
• Reporting across property sets is more difficult because the underlying data is separated.
Use this scenario when: the grouping must form a genuine operational data boundary, not merely a convenient filter.
Separate countries or legal entities
Advantages
• Data ownership and visibility can follow organizational or geographical boundaries.
• Separate property sets can support privacy, governance, and contractual requirements.
• New entities can be added without creating a separate Planon installation for each one.
Disadvantages
• Reports, configurations, mobile applications, and service desk components may require separate setup for each property set.
• Interfaces must identify the relevant property set and route every message correctly.
• Cross-property-set reporting and consolidated KPIs require additional design.
• Workflow and feature settings remain shared.
Use this scenario when: countries or legal entities use a shared Planon platform but require strong separation of operational data.
Separate customers in a service provider environment
A service provider can use separate property sets for customers that share one Planon environment. This keeps each customer’s operational data in a separate data domain.
Advantages
• Customer data is segregated within the shared environment.
• Each customer can have property-set-specific operational settings.
• The architecture can support the onboarding of additional customers or organizational units.
Disadvantages
• Configuration and maintenance effort increases with every property set.
• Shared workflows limit the degree to which customers can operate as fully independent tenants.
• Significant differences in customer-specific functionality or customization can result in configuration drift.
• Additional licensing considerations may apply, particularly in cloud environments.
Use this scenario when: customers must share a platform while their operational data must remain segregated.
Separate data for legal or contractual reasons
Property sets can be used when operational data must be separated more strongly than can reasonably be achieved through authorization filters alone.
Data and settings associated with a property set