# Perspective Property Access Modes

**URL:** <https://forum.inductiveautomation.com/t/perspective-property-access-modes/97927>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 29, 2024, 9:53pm UTC](https://forum.inductiveautomation.com/t/perspective-property-access-modes/97927 "2024-10-29T21:53:55Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![salbrechtsen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/salbrechtsen/32/18660_2.png) [@salbrechtsen](https://forum.inductiveautomation.com/u/salbrechtsen)\
**Post date:** [April 11, 2025, 10:57pm UTC](https://forum.inductiveautomation.com/t/perspective-property-access-modes/97927/5 "2025-04-11T22:57:57Z")

</div>

[I've been discussing this with others](https://forum.inductiveautomation.com/t/page-vs-session-props-security/104595/19) and really thing public custom properties should be an opt in.

Honestly, view parameters seems like they would want to be private or at least protected.

I'm planning to write a script to set all of our custom props to private in the view JSON files on the gateway. Would doing this to view params also be safe as well? I basically only want view params and custom props to be set in our bindings and scripts, never from the browser.

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-property-access-modes/97927)._