# Permissions on custom session properties

**URL:** <https://forum.inductiveautomation.com/t/permissions-on-custom-session-properties/114861>\
**Category:** Ignition\
**Tags:** perspective, scripting\
**Created:** [April 2, 2026, 2:35pm UTC](https://forum.inductiveautomation.com/t/permissions-on-custom-session-properties/114861 "2026-04-02T14:35:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![parker.williams](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@parker.williams](https://forum.inductiveautomation.com/u/parker.williams)\
**Post date:** [April 2, 2026, 7:51pm UTC](https://forum.inductiveautomation.com/t/permissions-on-custom-session-properties/114861/7 "2026-04-02T19:51:53Z")

</div>

I agree, and I appreciate your insight. When I say "legacy", I mean at least 10-20 years. I know that's not much for some people but it is for me.

I'll look into whether I can redesign the existing database. The existing codebase isn't the most straightforward which is the reason for me porting it to Ignition.

I guess all that I need is just a way to make these properties not visible or writable to an end user. After changing them to private I can still see them in the dev console.

---

_[View the full topic](https://forum.inductiveautomation.com/t/permissions-on-custom-session-properties/114861)._