# Ignition edge single project restriction **URL:** \ **Category:** General Discussion\ **Tags:** ignition81\ **Created:** [January 25, 2025, 8:52am UTC](https://forum.inductiveautomation.com/t/ignition-edge-single-project-restriction/101383 "2025-01-25T08:52:07Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [January 27, 2025, 6:27pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-single-project-restriction/101383/11 "2025-01-27T18:27:58Z")
Probably just keep everything inheriting from Common. I'm not sure what you're currently planning to inherit from Site N Data to All Sites GUI (Views? Named Queries?), but most likely it's something that you can put in Common and use parametrization to be able to use the Site A, B, or C version. Something like the below: > [@How to Inherit resources from multiple projects](https://forum.inductiveautomation.com/t/how-to-inherit-resources-from-multiple-projects/70764/2): > > You cannot do this as drawn. There is no multiple inheritance (water under the bridge). You will need two "admin" projects, and move graphics from the current leaf projects: Create an inheritable "admin" base project with all projects' graphics. Possibly in the Library project, but I'd make it separate, inheriting the Library. Organize per-project resources into folders for convenience. Restructure the leaf projects to only have the unique nav elements they need. Create a non-inheri… EDIT: The multiple inheritance issue has come up multiple times before, with a couple of different workarounds depending on the situation, so here's another workaround: > [@Project Multiple Inheritance](https://forum.inductiveautomation.com/t/project-multiple-inheritance/26432/8): > > While Ignition only allows for single-inheritance, there is nothing stopping you from chaining inheritance into a sort of ancestry structure. ProjectA: includes resources which EVERY project should have access to. ProjectB: inherits from ProjectA. is intended for use by projects for CustomerA, and so has its default database set to CustomerA's database. contains resources like Views and scripts which are specific to only CustomerA. ProjectC: inherits from ProjectB. is a front-end/runnab… So you could also try some chain of Common -\> A -\> B (now AB) -\> C (now ABC) -\> All Sites and have some unnecessary resources floating around in your B and C that only exist to be inherited by your All Sites. --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-edge-single-project-restriction/101383)._