# Login Authentication Restrictions To Components **URL:** \ **Category:** Ignition\ **Created:** [November 2, 2023, 2:10pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387 "2023-11-02T14:10:05Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dcan87](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dcan87/32/54071_2.png) [@dcan87](https://forum.inductiveautomation.com/u/dcan87)\ **Post date:** [November 2, 2023, 2:10pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/1 "2023-11-02T14:10:05Z")
I have a pop-up that is triggered on double click of subview in a table, with drop-down components that write to memory tags when changed. I would like the ability to change those controlled through login authentication. On my main page view, I have placed a login/log out button. It is functioning correctly. I have added the isDisabled property to my data options in the dropdown component and tried a couple different methods but no luck: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/0/30bd6f59198edb46013cd06b15c32d3fa6dead13.png) ---
**Author:** ![kyler.kamyszek](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@kyler.kamyszek](https://forum.inductiveautomation.com/u/kyler.kamyszek)\ **Post date:** [November 2, 2023, 2:20pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/2 "2023-11-02T14:20:03Z")
You can add the security measure on the double click action of the table. Switch your action to be a script and use the system.perspective.popup function to open your popup. You will see the security option at the bottom of the window. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/7/e78cf89d0cec006010cb0cd96f3994d33e440395.png) ---
**Author:** ![dcan87](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dcan87/32/54071_2.png) [@dcan87](https://forum.inductiveautomation.com/u/dcan87)\ **Post date:** [November 2, 2023, 2:42pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/3 "2023-11-02T14:42:41Z")
> [@kyler.kamyszek](#): > > d the security measure on the double click action of the t I still need the popup to open for an un-authenticated user but just have the ability for them not to change the dropdowns on the popup. Looks like I can still use your method and add a onClick event script on the dropdown component. Just not sure what my script should say in order to toggle 'isDisabled' property based on authentication? ---
**Author:** ![Hayden\_Watson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hayden_watson/32/48792_2.png) [@Hayden\_Watson](https://forum.inductiveautomation.com/u/Hayden_Watson)\ **Post date:** [November 2, 2023, 2:46pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/4 "2023-11-02T14:46:31Z")
You can add a binding on the `props.enabled` to prevent use of the component. To make certain you can also set who has read/write permissions for tags in the tag configuration. ---
**Author:** ![dcan87](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dcan87/32/54071_2.png) [@dcan87](https://forum.inductiveautomation.com/u/dcan87)\ **Post date:** [November 2, 2023, 4:11pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/5 "2023-11-02T16:11:14Z")
Not enough detail for my experience level to follow sorry. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [November 2, 2023, 4:43pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/6 "2023-11-02T16:43:52Z")
Every `Input` category component has a property named `enabled` at the top level of `props` (`tagQualityDropdown.props.enabled` in your View) which is used to determine when a component may be interacted with. This property dictates the enabled state of the entire component, preventing users from even expanding the dropdown if they don't meet the conditions you set forth. We have testing around the `isDisabled` property, so it is behaving as expected, and your issue is far more likely to be a discrepancy in how your `tagQualityDropdown.custom.auth` property is being defined. It's very likely that in the Designer you've got the property as `true` (and are therefore seeing your expected `false` value), but in the running session that property is not being set as expected (and therefore entering the fallback `true` case). One way to simplify this is to bind `tagQualityDropdown.props.enabled` with a binding against `session.props.auth.authenticated`. ---
**Author:** ![dcan87](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dcan87/32/54071_2.png) [@dcan87](https://forum.inductiveautomation.com/u/dcan87)\ **Post date:** [November 2, 2023, 5:54pm UTC](https://forum.inductiveautomation.com/t/login-authentication-restrictions-to-components/81387/7 "2023-11-02T17:54:53Z")
Thank you! I saw the enabled property but was looking to quick and thought it was under the placeholder hierarchy. Thanks again!