# Perspective user preference

**URL:** <https://forum.inductiveautomation.com/t/perspective-user-preference/101445>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [January 27, 2025, 7:30pm UTC](https://forum.inductiveautomation.com/t/perspective-user-preference/101445 "2025-01-27T19:30:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [January 27, 2025, 7:38pm UTC](https://forum.inductiveautomation.com/t/perspective-user-preference/101445/3 "2025-01-27T19:38:11Z")

</div>

Nothing with cookies yet, you'll have to utilize your DB and session custom properties.

> [@Save/restore component properties to DB](https://forum.inductiveautomation.com/t/save-restore-component-properties-to-db/88383/9):
>
> Correct. To make it sticky, save/load from the DB. I'd say this is much easier and more transparent than diving into using SDK functions, especially if you get another engineer who knows nothing about the project/customization data. (That's my opinion anyways). It would also essentially 'live' in only one or two places, the session startup handler and the user id value change event, as opposed to every component that needed some sort of customization. You could have a structure something alo…

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-user-preference/101445)._
