This is an overview of domain separation and Project Portfolio Management. With
domain separation you can 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 level: Basic
- Business logic: Ensure that data goes into the proper domain for the application’s
service provider use cases.
- The application supports domain separation at run time. This includes domain
separation from the user interface, cache keys, reporting, rollups, and aggregations.
- The owner of the instance must set up the application to function across multiple
tenants.
Use case: When a service provider (SP) uses chat to respond to a tenant-customer’s
message, the client must be able to see the SP's response.
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.
