# Containers enable affects children components **URL:** \ **Category:** Ignition\ **Created:** [June 15, 2011, 1:30am UTC](https://forum.inductiveautomation.com/t/containers-enable-affects-children-components/3012 "2011-06-15T01:30:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Joseph\_Mendonca](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@Joseph\_Mendonca](https://forum.inductiveautomation.com/u/Joseph_Mendonca)\ **Post date:** [June 15, 2011, 1:30am UTC](https://forum.inductiveautomation.com/t/containers-enable-affects-children-components/3012/1 "2011-06-15T01:30:58Z")
Going through the forums there are several posts that discuss this issue of disabling the container also disables all of its children. However, enabling the the container does not do the same for the children. Is it possible to have an option put into the container that could, if enabled, have the children adhere to the enable/disable of the parent container? ---
**Author:** ![ISDProj](https://avatars.discourse-cdn.com/v4/letter/i/58956e/32.png) [@ISDProj](https://forum.inductiveautomation.com/u/ISDProj)\ **Post date:** [June 15, 2011, 2:00am UTC](https://forum.inductiveautomation.com/t/containers-enable-affects-children-components/3012/2 "2011-06-15T02:00:19Z")
I agree with Joseph on this but I’d see that the “enabled” property would need to be tri-state e.g. yes/no/inherited. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [June 15, 2011, 7:13pm UTC](https://forum.inductiveautomation.com/t/containers-enable-affects-children-components/3012/3 "2011-06-15T19:13:48Z")
Yeah, we’re going to change the security settings so that they aren’t so directly tied to the enabled property. See also [this feature request](http://www.inductiveautomation.com/forum/viewtopic.php?f=71&t=6505&p=18573).