Application Timeout

Short Description Hive9 sessions time out after a period of inactivity. This article covers the timeout range, the default, and how to change it.

What this article answers

What Application Timeout controls.
The valid range and default.
How and where to change it.

What it controls

Application Timeout is the period of user inactivity after which Hive9 ends the user's session and signs them out. The user has to log in again to continue.

A session is active when the user is interacting with Hive9 — clicks, navigation, edits.
A session goes inactive when there's no user interaction.
After the timeout window expires on an inactive session, Hive9 forcibly ends it.

This is a security control — it prevents abandoned sessions from sitting logged-in indefinitely on shared or public devices.

The valid range

Minimum: 10 minutes.
Maximum: 120 minutes (2 hours).
Default: 60 minutes (1 hour).
Whole numbers only — no fractions.

How to change it

Go to Settings → Organizational Setup → App Configurations.
Find Application Timeout.
Enter the new value (10–120, whole number).
Save.

The change applies to all users on next session.

Changes are recorded in the audit log with the prior and new values, the user who changed it, and the timestamp.

Picking a timeout value

Shorter timeouts (10–30 minutes) work well when…

Users access Hive9 from shared devices or public locations.
Your organization has strict security policies on inactive sessions.
The work pattern is short bursts followed by long breaks.

Standard timeouts (45–60 minutes) work well when…

Most users work from their own devices.
The work pattern includes some idle time but mostly active use.

Longer timeouts (90–120 minutes) work well when…

Users frequently switch between Hive9 and other tools for long stretches.
Re-logging-in is a significant friction.
Your organization's security policies allow longer sessions.

What users experience at timeout

Hive9 ends the session in the background.
On next interaction (click, navigation), the user is redirected to the login screen.
Unsaved edits are typically lost (Hive9 doesn't auto-save).
Users have to log back in to continue.

Users can mitigate the impact by saving frequently and using Saved Views for quick restoration of their work context.

Common questions

Can different users have different timeouts? No — Application Timeout is instance-wide. All users share the same value.

Does the timeout affect SSO sessions? The Hive9 session ends per the timeout. The user's IdP session may still be active, in which case the next login is faster (no IdP re-authentication needed).

What about admin sessions? Same timeout applies — no special exception for admins.

Will users be warned before timeout? Hive9 may show a session warning before ending — depends on your version. The user can extend by interacting with the application.