# Ignition Hub and Spoke Layout - Discussion **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [May 26, 2023, 1:18pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219 "2023-05-26T13:18:40Z")\ **Posts on this page:** 5\ **Page:** 2
**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:** [June 2, 2023, 6:11pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219/21 "2023-06-02T18:11:17Z")
> [@amarks](#): > > I don't think that's possible with the single project inheritance Yes, multiple inheritance would be very, very nice. ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [June 6, 2023, 4:47pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219/22 "2023-06-06T16:47:35Z")
So then the solution _ **is not** _ to have multiple smaller projects. The solution is to have one big project and trim down for different zones/areas/departments as needed. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [June 6, 2023, 5:42pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219/23 "2023-06-06T17:42:25Z")
Whatever you call it, the inherited projects, zones/depts and global, only hold what is _common and should be shared._ The child projects are where you put specific resources and constraints that are needed for those projects, like security settings. IE a named query that should be available to all projects goes into `global` from my example, and a named query that is specific to only `department2` projects goes into the department2 project, and likewise for the final projects. Shared views are in the global and zone projects, exclusive views go into the child projects where applicable. As you move down the inheritance tree, the more specific your resources should become. ---
**Author:** ![dmachuca](https://avatars.discourse-cdn.com/v4/letter/d/a8b319/32.png) [@dmachuca](https://forum.inductiveautomation.com/u/dmachuca)\ **Post date:** [October 14, 2024, 1:41pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219/24 "2024-10-14T13:41:21Z")
Which approach did you decide on? I’m encountering a similar situation and could use some insight. ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [October 14, 2024, 1:52pm UTC](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219/25 "2024-10-14T13:52:05Z")
We have one project that runs on a main Ignition server (full Ignition). There are 5 computers that function as clients and also have Ignition Edge for fallback. - Each edge gateway is configured with only the device connections for that "local area." - Each edge gateway runs the same project as the main Ignition server as the fallback. - The project is set up to show/hide/disable navigation on specific screens based on the area that is determined by which devices are connected to the gateway. (all = master, 1,2,3 = area 1, 4,5,6 = area 2... etc.). - Each "area" also has it's own tag provider on the master gateway. This ends up being the only tag provider that is on the edge for fallback. Each edge gateway is connected to the central gateway with EAM. - There are tasks to "send" UDT definitions between the providers on the master gateway - triggered manually when UDT definitions are updated. - There are tasks to send the tags in each tag provider from the master to the corresponding gateway. - There is a task to send the project to each edge gateway. Needs some scripting to get trend pens for tags to automatically update their history path based on which gateway the project is running from (full or Edge gateway). [Previous page](https://forum.inductiveautomation.com/t/ignition-hub-and-spoke-layout-discussion/74219.md?page=1)