Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Domain separation in Project Portfolio Management

Log in to subscribe to topics and get notified when content changes.

Domain separation in Project Portfolio Management

This is an overview of domain separation and Project Portfolio Management. Domain separation enables 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.


Support: Data only

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 separation.

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 supported.
  • 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.