Account Time Outs/Locking/Freezes should be timed from the last action on the system rather than the logon time (or at least there should be the options).
Hi all, just an update on this feedback item; I’ve been working on a little something that might solve this. Without getting too nerdy about how our authentication layer works I’ve put together a prototype where we automatically extend your Plannr session with usage, as long as you’re using the system (e.g. navigating) and not sat on a page. The code will auto-extend your session if you’re within 15 minutes of when the expiry warning appears. We’re going to test this internally and then roll out if it passes muster.
Gavin Porritt
•
Nov 20, 2025
Hi Gareth,
Just checking whether there was any further progress on this as I guess the initial solution didn’t pass muster?
Hugh Hawkins
•
Mar 4, 2025
We’d love for this to be fixed. Timing out based on login time makes no sense, a time out since last activity is the correct way to do this.
Log in to comment and vote
Comments3
Gareth (G) Thompson
Mar 24, 2025
Hi all, just an update on this feedback item; I’ve been working on a little something that might solve this. Without getting too nerdy about how our authentication layer works I’ve put together a prototype where we automatically extend your Plannr session with usage, as long as you’re using the system (e.g. navigating) and not sat on a page. The code will auto-extend your session if you’re within 15 minutes of when the expiry warning appears. We’re going to test this internally and then roll out if it passes muster.
Gavin Porritt
Nov 20, 2025
Hi Gareth,
Just checking whether there was any further progress on this as I guess the initial solution didn’t pass muster?
Hugh Hawkins
Mar 4, 2025
We’d love for this to be fixed. Timing out based on login time makes no sense, a time out since last activity is the correct way to do this.