# Ignition Perspective auto-sync between two different projects on the same gateway

**URL:** <https://forum.inductiveautomation.com/t/ignition-perspective-auto-sync-between-two-different-projects-on-the-same-gateway/103647>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 13, 2025, 5:35pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-auto-sync-between-two-different-projects-on-the-same-gateway/103647 "2025-03-13T17:35:12Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 13, 2025, 7:50pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-auto-sync-between-two-different-projects-on-the-same-gateway/103647/5 "2025-03-13T19:50:55Z")

</div>

Based on your edit, I see you've described an inheritance hierarchy. You just need to mark project "A" as inheritable and set "B" to inherit from "A". Remove resources from "B" that are duplicates of "A". No further synchronization required.

> **[Project Inheritance | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/projects/project-inheritance)**
>
> Project Inheritance allows one project to inherit resources from another project. If you have project resources that you want other projects to use such as views, windows, scripts, templates, or pipelines, you can create an inheritable project...

Note that this is **single** inheritance, not true library-style multiple inheritance. You may wish to follow my advice described here:

> [@Where do/should Gateway Scripts live with respect to an inherited project structure?](https://forum.inductiveautomation.com/t/where-do-should-gateway-scripts-live-with-respect-to-an-inherited-project-structure/83460/3):
>
> Put all of the logic in project library scripts, in the "universe" project at the root of your hierarchy, if you must. Then, in leaf projects, use one-line calls to the appropriate logic from event scripts and message handlers. (I don't agree with your desire, but this is what you must do to achieve it.) I recommend you not put all your scripts (eggs) in one inheritable project (basket). I recommend a hierarchy something like this: universe ├bg\_common │├gsp │├background1 │├background2 │└we…

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-perspective-auto-sync-between-two-different-projects-on-the-same-gateway/103647)._
