# User session props always null in designer

**URL:** <https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055>\
**Category:** Ignition Early Access\
**Created:** [March 13, 2020, 4:13am UTC](https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055 "2020-03-13T04:13:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [March 13, 2020, 4:13am UTC](https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055/1 "2020-03-13T04:13:05Z")

</div>

Hi  
When login to designer and editing perspective project it is nice if in session props show the current user info display instead of null value.  
It is really hard and annoying when designing object in perspective with security on it that bind to user session info value in designer. The object get error overlay to it and it is not possible to test and see final result untill see project in browser.  
Yes I know designer is not session but still the perspective editing environment is a broswer. So it is good to have corrent user name in session user props.

---

<div class="post-metadata">

**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:** [March 13, 2020, 2:07pm UTC](https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055/2 "2020-03-13T14:07:09Z")

</div>

You could always copy that `user` object and make a new session custom property out of it. Now, supply values you might expect for a known user, or values you’d like to test; this will allow you to design around known info. When you’re done, bind the custom `user` object to the true object.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [March 14, 2020, 5:12am UTC](https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055/3 "2020-03-14T05:12:33Z")

</div>

Clever idea. Any way why IA fill them null in designer?

---

<div class="post-metadata">

**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:** [March 16, 2020, 2:28pm UTC](https://forum.inductiveautomation.com/t/user-session-props-always-null-in-designer/33055/4 "2020-03-16T14:28:47Z")

</div>

1. They must always be expected to be present.
2. They must always be expected to be manipulated directly by the system, and not a user/scripts/bindings.
3. Allowing a Designer user to manipulate those properties in the Designer and make changes based off of these changes can easily result in important differences in behavior between the Designer and a runtime environment.
4. Having them attached to the user who is logged into the Designer could also result in situations where the Designer would behave one way, while a runtime session would behave differently.