This is an overview of domain separation as it applies to Project Portfolio Management.
separation allows you to separate data, processes, and administrative tasks into logical
groupings called domains. You can then control several aspects of this separation, including
which users can see and access data.
Domain separation provides complete data isolation for domain-specific users. Domain separation in this
application is supported at the Data only level, meaning it
supports the data security model of separating visibility of data from one domain to
another. To learn more, see Application support for domain
How domain separation works in Project Portfolio Management
Project Portfolio Management is domain separation-compliant with the following limitations:
- All PPM entities such as project, demand, resource plan, and allocations are expected to be
in the same domain. A project entity having tasks or resources from multiple domains is not
- A parent entity and all child entities, such as a project record and its project tasks, are
expected to be in the same domain.
- When you change the domain of a parent record, for example a project record, the domain of
the child records are not changed.
- Only users belonging to the same domain, parent domain, or the top domain have the
visibility into PPM entities of a domain.
- All system properties are in the global domain and are not specific to a domain. Planning
console settings, however, are still domain-specific.