What determines Figma's per-session idle timeout duration across collaborative sessions?

Figma's real-time collaboration model relies on per-session idle detection to gracefully disconnect users after periods of inactivity, thereby preserving unsaved work and informing other participants through presence updates. The mechanism governs when a client is considered idle and triggers a disconnect sequence that other users observe via the presence payload.

However, the precise criteria triggering this timeout—including the idle duration threshold, the role of cursor or viewport activity, and whether the behavior differs between editing and viewing modes—remain unspecified in public documentation. This ambiguity poses challenges for enterprises seeking to align Figma's session lifecycle with internal idle‑session policies or single‑sign‑on lifecycle events. The exact threshold is unverified and subject to client‑side implementation differences.

• What idle‑duration threshold does Figma apply before considering a session inactive?
• Does the timeout differentiate between active editing and passive viewport viewing?
• Can the timeout behavior be influenced or overridden through API parameters or organization‑wide configuration?