# Onboarding/Welcome screen

**URL:** <https://community.glideapps.com/t/onboarding-welcome-screen/61686>\
**Category:** Ask for Help\
**Created:** [May 12, 2023, 1:31pm UTC](https://community.glideapps.com/t/onboarding-welcome-screen/61686 "2023-05-12T13:31:02Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [May 12, 2023, 2:31pm UTC](https://community.glideapps.com/t/onboarding-welcome-screen/61686/5 "2023-05-12T14:31:54Z")

</div>

That’s a tough one. That’s one case where session variable columns would be useful because they would reset regardless if you are signed in or not.

> [@Session Variable Column](https://community.glideapps.com/t/session-variable-column/40260):
>
> I’ve always thought that it’s really useful how user specific columns only store values locally and for the duration of your session while you are not signed in. This allows for those column values to “reset” after you close the app, and the data does not need to be sent and synchronized with glide servers. However, once you sign in, then those values are sent to, and stored, on Glide’s servers. I think a new Session column type could be really useful. It would work just like user specific c…

Only other thought would be to set a date/time when the button is clicked, and then set your tab visibility conditions to expire after a certain number of hours. Not the best solution though.

---

_[View the full topic](https://community.glideapps.com/t/onboarding-welcome-screen/61686)._
