I'm not sure if there's an elegant way to do it. I have not tried the below.

The only thing that comes to mind would be to create some dodgy solution where you're comparing values in the database against the defualt session timeout duration to then build a function that executes to evaluate whether the user is still logged in or not.

For exmaple... instantiate a variable upon page load that pulls the user_CRM_SID value from the database on load (or pulls from the URL), compares the SID to the activity table (to see when the Acty_LastAction occurred), pulls the session timeout varaible from the settings, and then has a script that compares the current time with the last action time + session timeout variable converted to milliseconds, waits the duration of the calculated session timeout to evaluate the current SID for the user to then either remain on the page or re-route to the login.

It would be hacky AF, but it could work. I just have no idea what level of risk this could impose or how resourceful it might be. 

Alternatively, you could just isolate the message that people are seeing and prevent it specifically from displaying. It really depends what you're trying to focus on - User experience from a "how does it work?" vs. "how does it look?"

I'm not sure if there's an elegant way to do it. I have not tried the below.

The only thing that comes to mind would be to create some dodgy solution where you're comparing values in the database against the defualt session timeout duration to then build a function that executes to evaluate whether the user is still logged in or not.

For exmaple... instantiate a variable upon page load that pulls the user_CRM_SID value from the database on load (or pulls from the URL), compares the SID to the activity table (to see when the Acty_LastAction occurred), pulls the session timeout varaible from the settings, and then has a script that compares the current time with the last action time + session timeout variable converted to milliseconds, waits the duration of the calculated session timeout to evaluate the current SID for the user to then either remain on the page or re-route to the login.

It would be hacky AF, but it could work. I just have no idea what level of risk this could impose or how resourceful it might be. 

Alternatively, you could just isolate the message that people are seeing and prevent it specifically from displaying. It really depends what you're trying to focus on - User experience from a "how does it work?" vs. "how does it look?"