What User Activities Reset the Logout Timer in Jama Connect?

Author: Kemi Lewis
Date: 23 June 2025

Audience: Jama Connect® Org Admins, IT Help-Desk Staff, Project Leads, Power Users

Products Applicable: Jama Connect® (Cloud & Self-Hosted)

Use Case

What User Activities Reset the Logout Timer in Jama Connect?

Best Practice

Only interactions that generate a client-to-server event—such as a click, navigation, or an explicit save—reset Jama Connect’s inactivity timer. Passive actions (typing without saving, scrolling, and hovering) do not. Teach users to click Save or shift focus periodically during long edits, and set reasonable admin timeout values to minimize unexpected logouts.

Implementation

Activity Category	Examples	Resets Timer?	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 Save periodically to avoid timeout.
Background Tab	Jama tab left idle while user works elsewhere	❌ No	Browser throttles inactive tab—timer continues.

Admin Configuration

Set Inactivity Time-out
- Root Admin → System Properties → License (Cloud) or jama-cfg.properties (Self-Hosted)
- Typical range: 30–60 minutes.
Notify Users
- Add a quick-tip in onboarding docs: “A click or save resets your timer; typing alone does not.”
Optional Browser Extension
- Deploy org-wide notification to warn users 2–5 minutes before timeout.

References

Please feel free to leave feedback in the comments below.

Related to