Session Timeout - Vizcom Docs

What is Session Timeout?

Session timeout is an Enterprise-only security feature that automatically ends a member’s session after a set period of inactivity. It is configured by Org Admins and applies to all members of the organization. When enabled, Vizcom monitors user activity and starts an inactivity timer when no interaction is detected. If the timer runs out without the member responding, they are automatically logged out. Use session timeout to reduce the risk of unattended sessions leaving sensitive design work accessible.

How to use Session Timeout:

Configuring session timeout (Org Admins on Enterprise plan only):

  1. Navigate to Organization Settings.

  2. Select the Security tab.

  3. Find the Session Timeout section.

  4. Use the dropdown to select a timeout duration: Never, 1 hour, 2 hours, 4 hours, 8 hours, 12 hours, or 24 hours.

  5. Changes take effect immediately for all members of the organization.

What members experience when a session is about to expire:

  1. After the configured period of inactivity, a warning modal appears 5 minutes before the session ends.
  2. The modal displays a countdown timer and two options: Stay logged in or Log out now.
  3. Clicking Stay logged in extends the session. Clicking Log out now ends it immediately.
  4. The modal cannot be dismissed — one of the two options must be selected.
  5. If no action is taken before the timer runs out, the member is automatically logged out across all open browser tabs.

Core Features:

Inactivity Tracking

Warning Modal

Cross-Tab Sync

Multiple Organization Handling

Tips & FAQ

FOR ADMINS: Design workflows often involve periods of thinking without direct computer interaction. Consider your team’s working patterns when choosing a timeout duration, and notify your team before enabling or changing the setting.

FOR MEMBERS: Save your work frequently. If a session expires before saving, unsaved changes will be lost. When stepping away from your desk, logging out manually is the safest option rather than waiting for the timeout.

FAQ

Next Steps: