# Version 8 Shared Vision Templates **URL:** \ **Category:** Ignition\ **Created:** [April 18, 2019, 4:34pm UTC](https://forum.inductiveautomation.com/t/version-8-shared-vision-templates/24239 "2019-04-18T16:34:13Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 18, 2019, 9:28pm UTC](https://forum.inductiveautomation.com/t/version-8-shared-vision-templates/24239/11 "2019-04-18T21:28:33Z")
So, it’s important to understand what the new inheritance system actually implies. There are two separate projects in play, after an upgrade: `global` - where previously “global” resources lived. This defines a set of resources (including shared templates, etc) `` - which _inherits_ from the `global` project. Those inherited resources _act_ as if they’re actually present in `` - _but_ they cannot be edited, because they’re not actually there. If you want to make modifications, you have two options: 1. Right click the ‘greyed out’ resource to override it. This creates a _copy_ of the parent’s resource definition, only this copy is actually inside your project, meaning you can edit it. The downside to doing this often is that you aren’t changing things in a “global” way. 2. Open the `global` project and make your edits there. Then, the next time you pull in changes in ``, you’ll get an updated inherited resource. It’s still not _actually_ in ``, but you can use it as if it was. It’s a different way to think about inheritance from what we had before, but it’s incredibly more powerful and flexible. I’ll make a note to have someone double check that template upgrading is working as expected, but so far it does appear that it is. --- _[View the full topic](https://forum.inductiveautomation.com/t/version-8-shared-vision-templates/24239)._