Skip to main content
Available on Enterprise plans.
Each time you open a connection, Deck authenticates the user against the source. With persistence enabled, Deck saves the authenticated session so future connections to the same source skip login and MFA. Persisted sessions are subject to the source’s own expiration policies. Some sources keep sessions alive for weeks, others invalidate them after minutes. Persistence is a best-effort optimization that Deck manages for you.

​
How it works

When persistence is enabled on a connection:
  1. The user authenticates normally when the connection is created
  2. Deck saves the authenticated session state after login succeeds
  3. On the next connection open, Deck restores the saved session
  4. If the session is still valid at the source, the connection is ready without re-authenticating
  5. If the session has expired, the connection returns interaction_required so the user can re-authenticate

​
Enabling persistence

Persistence can be enabled per-connection through the API or Dashboard. This feature is available on Enterprise plans.

​
Source-specific behavior

Session lifetime is determined by the source. Each source has its own policies around session expiration, and these can change without notice.
FactorImpact
Session timeoutSome sources expire sessions after 15 minutes of inactivity. Others keep them alive for 30 days.
Security eventsPassword changes, MFA resets, or suspicious activity flags at the source can invalidate sessions immediately.
Persistence works best for sources with long-lived sessions. For sources that aggressively expire sessions, Deck falls back to re-authentication more often.