# Disable window override ability

**URL:** <https://forum.inductiveautomation.com/t/disable-window-override-ability/80806>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [October 21, 2023, 5:14pm UTC](https://forum.inductiveautomation.com/t/disable-window-override-ability/80806 "2023-10-21T17:14:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bwhite](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bwhite/32/7112_2.png) [@bwhite](https://forum.inductiveautomation.com/u/bwhite)\
**Post date:** [October 21, 2023, 5:14pm UTC](https://forum.inductiveautomation.com/t/disable-window-override-ability/80806/1 "2023-10-21T17:14:09Z")

</div>

Is there a way to not allow global resources to be edited in the child project? in particular, Vision Window that are in the global project.

---

<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:** [October 21, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/disable-window-override-ability/80806/2 "2023-10-21T17:26:37Z")

</div>

Nope. But you could detect that it happened by scanning the gateway filesystem. Perhaps including such in a project library script.

---

<div class="post-metadata">

**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:** [October 21, 2023, 6:09pm UTC](https://forum.inductiveautomation.com/t/disable-window-override-ability/80806/3 "2023-10-21T18:09:46Z")

</div>

[Protecting](https://docs.inductiveautomation.com/display/DOC81/Project+Security+in+the+Designer#ProjectSecurityintheDesigner-ProtectingProjectResources) the resource might be a sufficient workaround. That is, mark them as protected in the global project and ensure that designers in the child project don't have permissions to unprotect. I can't remember enough specifics to remember if that's anything more than a minor speedbump though.