Published Date: September 8, 2025
Audience: Everyone
Products and Versions Covered:
- Jama Connect® version(s) 9.25 and above
- Cloud/CVC
- Self-hosted
Summary
This article provides a detailed explanation of Jama Connect®'s new feature, the User Inactivity Timeout.
Resolution
This new feature gives Organization Admins more control over user inactivity timeout sessions. From the License page, Admins can now choose how long a user can remain inactive before automatically signed out. This is managed through a drop-down menu with preset options ranging from 5 to 120 minutes.
Figure 1.0 - This example shows the User Inactivity Timeout set to 30 minutes.
By default, the inactivity timeout is set to 120 minutes, which matches the standard duration of a float license session. However, it’s important to note that changing the user inactivity timeout does not affect the length of the float license session-those remain valid for 120 minutes regardless of user inactivity.
The license timeout refers to the duration a float license remains active once it’s assigned to a user, it ensures that a license is automatically released after 120 minutes. The user inactivity timeout refers to how long a user can remain idle before being signed out. Changing the user inactivity timeout does not affect the license timeout-they operate independently. Another thing to note is that if a user is logged out due to inactivity, once they log back in they will consume the previous license. For example, if the user inactivity timeout is set to 5 minutes and the user is logged out because they were inactive, once they log back in they will still hold the same license they previously had for the remainder time of 115 minutes of the license session.
The user only releases the floating license if the 120 minutes expire or the user explicitly logs out by selecting log out inside the application. The session timeout due to inactivity is not an explicit logout so they retain the license. The user inactivity timeout corresponds to the amount of time a user can be idle before they are logged out. The license timeout refers to the amount of time, which is 120 minutes, a user can hold a float license. This setting can't be changed. If a user is logged out due to inactivity but their license timeout session hasn't expired yet, they still hold that float license until the 120 minutes is completed.
| Activity Category | Examples | Timer Reset | Guidance / Workaround |
| Active Clicks & Navigation | Selecting items, opening menus, pressing buttons, changing views | ✅ Yes | Normal interaction; no extra action needed. |
| Widget / Panel Interaction | Adding a comment, opening Versions or Relationships panels | ✅ Yes | Generates server call that restarts timer. |
| Field Focus + Save | Clicking into a field and clicking Save or shifting focus | ✅ Yes | Encourage “save early, save often.” |
| Typing Only | Continuous typing in a rich-text or plain-text field without saving | ❌ No | Press Save or click outside the field every few minutes. |
| Mouse Movement / Hover | Moving cursor, hover tooltips, drag-select without dropping | ❌ No | Movement alone is ignored by heartbeat script. |
| Scrolling Only | Mouse-wheel, track-pad, scrollbar movement | ❌ No | Scroll plus a click somewhere resets timer. |
| Full-Screen RTE Editing | Typing in full-screen rich-text editor for long duration | ❌ No | Exit fullscreen or click Saveperiodically to avoid timeout. |
| Background Tab | Jama tab left idle while user works elsewhere | ❌ No | Browser throttles inactive tab—timer continues. |
Additional Resources (for all external articles)
- Success Programs
- Success Catalog
- Datasheets
- Request a Solution Offering or Training from the Success Catalog
Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.
Comments
0 comments
Please sign in to leave a comment.