Summary

ClinSpark supports the ability to end a users' active session once a certain period of inactivity in the application has been reached. This session timeout period is defined per user account.

...

• Study > Lab Data

• Study > Report

• Study > Activity

• Data Collection > Subject

• Data Collection > Forms

• Volunteers > Recruit

• Samples > Processing

Limitations

As a web application, users are able to open and perform actions across multiple browser tabs or windows. This is not a common expectation for data collection workflows and is generally not recommended due to the issues this can bring with user session management and cross-study workflows. More of that is explained here: https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3700260899/Technical+Overview#Session-Management

The user timeout feature is also currently limited by this use case. If users have multiple windows or tabs open, each of those are independently considered for active session timeout periods. This means that it is possible an active session may be expiring (or already expired) in a window/tab currently not in active view or use. If a session were to timeout in one of those tabs/windows, the next action taken by a user may force them out of application in whatever window/tab they continue to use elsewhere.