Based on this:
Quote (Matt_Sharpe @ Jan 26 2016 10:16am)
I am able to access it on different browsers and they have individual timers so I can kind of work around it with mozzila and chrome, but would rather just not have to deal with it period.
It's pretty safe to assume it's linked to your session. Session variables are typically assigned when you log in and are not shared between browsers (obviously). Hence the timer difference per browser.
If the timeout is being assigned on login, you're out of luck without a unique script negating the session var. Which, they probably have security so it's a waste of time.