# Perspective run script after inactivity timer elapses

**URL:** <https://forum.inductiveautomation.com/t/perspective-run-script-after-inactivity-timer-elapses/43865>\
**Category:** Ignition\
**Tags:** ignition80, perspective\
**Created:** [February 26, 2021, 1:49pm UTC](https://forum.inductiveautomation.com/t/perspective-run-script-after-inactivity-timer-elapses/43865 "2021-02-26T13:49:30Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [March 25, 2024, 11:17am UTC](https://forum.inductiveautomation.com/t/perspective-run-script-after-inactivity-timer-elapses/43865/21 "2024-03-25T11:17:29Z")

</div>

You're right, from the script it's just a very basic timeout which is ideal for using the pre-packaged feature. In my case, I had more conditions like the Operator role could stay logged in but anything else couldn't, as well as some client-specific rules

[Previous page](https://forum.inductiveautomation.com/t/perspective-run-script-after-inactivity-timer-elapses/43865.md?page=1)