Recommendation
Use multiple property sets only when the organization needs a durable boundary between operational data domains, such as:
• Countries or legal entities whose data must remain segregated
• Customers managed by a service provider in a shared environment
• Organizational units with clear ownership and governance boundaries
• Scenarios in which authorization filters alone do not provide an appropriate segregation model
Do not introduce multiple property sets solely to hide selected records from particular users. If the requirement concerns only data visibility within one operational domain, prefer authorization and filtering. This avoids duplicated configuration, integration complexity, fragmented reporting, and additional maintenance.
Avoid multiple property sets when entities require independent workflows, substantially different customizations, or a level of regulatory isolation that demands separate systems. In these cases, separate Planon environments are more appropriate.
Make the decision early in the implementation. Introducing multiple property sets after the environment, integrations, numbering schemes, reports, and configurations have already been established can require substantial redesign and migration effort.
Decision rule
• Use one property set unless there is a clear and lasting requirement for strong operational data segregation.
• Use multiple property sets when the benefits of that segregation justify the additional architectural, integration, configuration, reporting, and governance complexity.