Skip to main content
Question

Auto-Logout

  • May 6, 2026 8:17 PM UTC
  • 3 replies
  • 77 views
Forum|alt.badge.img+6

Did QB recently (within the past few months) make any updates that would impact a user being auto-logged out due to inactivity? Admittedly this hasn't happened to me as I spend a big chunk of my day in QB, but I've had a lot of users complain that they've been getting logged out more and more often. Apparently they used to go the entire day without getting logged out (despite our realm-level policy being set at 2 hours of inactivity before triggering a log out), and now they're reporting as little as 30 minutes of inactivity before being asked to log back in again. It's a mild annoyance that's impacted a lot of my users.

Something I never really noticed because I hardly go 20 minutes without using QB during work hours, but maybe our 2 hour logout policy at the realm level wasn't being enforced properly and now it sort of is? 

    3 replies

    MarkShnierYou
    Forum|alt.badge.img+24

    There is a setting for that at the realm level, but if you can't find that setting or that setting is not available to you on your Plan level, you should be able to put in a support ticket and ask them to increase the auto logout time span. 

    Mark Shnier. Your Quickbase Coach
      RoyWanyoike
      Forum|alt.badge.img+13
      • RoyWanyoike
      • Registered
      • May 7, 2026 1:51 PM UTC

      I did notice too and thought its a feature. Or probably a security scrutiny which is controlled at the realm level.

      Roy Wanyoike
      Top Step
      Forum|alt.badge.img+9
      • Top Step
      • Registered
      • Oct 19, 2026 6:23 PM UTC

      The inactivity timeout itself is just the minutes set under Enable timeout for inactivity on the realm Policies tab, and users get a warning 60 seconds before the session closes. When people get bumped well before that, it's usually one of the other sign-in policies.

      Expire sessions after ___ minutes. This one has nothing to do with inactivity. It closes the session after a fixed time no matter what, so check it isn't set low.

      Concurrent session limit. If it's set, a new sign-in closes that user's oldest session. Someone working on a laptop, a second browser and the mobile app can knock themselves out without noticing. The inactivity timeout applies to mobile app sessions too.

      SSO. If you sign in with SAML, session length can come from the NotOnOrAfter attribute your identity provider sends instead of the realm policy, so a change on the IdP side would look exactly like this.

      To see what's happening for one user, open them in user management and go to the Sessions tab. It lists their active sessions with start and end times, IP address and browser.

      https://help.quickbase.com/docs/sign-in-policies

      https://help.quickbase.com/docs/session-management

      Top Step - https://www.topstep.tech/
      Terms & ConditionsAccessibility statement