Managing site ownership transfer and objects

The owning site is the site where the primary object of an object resides. It is the only site where the object can be modified. Therefore, to modify an object from a remote site, you must either transfer ownership of the object to your site or perform a remote checkout and edit an object.

When managing site ownership transfer and objects, consider the following:

• The owning user can transfer the ownership of any program or plan to another site. This will transfer the ownership of that program or plan and its events, along with the associated plan-level objects, to the other site.
• When exporting a program or plan with ownership transfer, the program, project, and its events will be transferred. Other artifacts such as program deliverables, risks, issue opportunities, checklists, etc. will not be transferred with ownership; instead they will be transferred as replica objects.
• Explicitly select program deliverables, risks, issue opportunities, checklists, etc., to transfer their ownership.
• When sharing individual child plan objects, such as a project with ownership transfer, the parent plan object (e.g., a program) will not be transferred. To ensure the project is properly loaded in the timeline at the shared site, it is recommended to share the program first and then share the child plan object.

Program Planning, 2606 — Unpublished work. © 2025 Siemens