There are various reasons why this can occur.

Staffpoint uses a general timeout of 20 minutes. It's counted by inactive time after you open certain page, or do certain actions. Mouse movements or typing are not counted as actions, however. These actions that can reset the timer include clicking a button on a page or navigating to a new page or section.

Lastly the current version of Staffpoint uses an old authentication method which can cause the user to be kicked out by many things, both server- and browser-related, including but not limited to:

  • The session can be destroyed or recycled on the IIS server
  • The browser can go into sleep mode and not reset the counter
  • Different tabs can be counted as different sessions
  • Server settings for session timeout can be lower than 20 min