How do automatic sign-outs work?

Idle users are warned, then signed out automatically — with separate timers per role and for the customer portal, all tuneable.

If someone leaves ResoFlow untouched for too long, they see a warning with a live countdown, then get signed out automatically — and you control how long "too long" is, per role.

The timers live in Settings → Security → Sessions and timeouts. Only Owners and Admins can change them; other staff see the values read-only.

• Open Settings → Security and expand Sessions and timeouts.
• Customer portal auto sign-out — how long a customer can be inactive in your customer portal before being signed out. Default 30 minutes, range 5–240; customers see a 5-minute warning first.
• Below it, set a timeout per role: Owner (default 30 minutes), Admin (30), Manager (60) and Host (and custom roles) (120). All accept 5–240 minutes — lower is more secure; higher means fewer mid-shift sign-ins.
• Click Save changes. Signed-in staff pick up the new values on their next page load.

What the person sees. Five minutes before the deadline, a warning pop-up appears with a countdown. Any activity — a click or typing — dismisses it and resets the timer; otherwise they're signed out and see a friendly explanation on the sign-in screen. Activity in one browser tab keeps your other tabs alive too, so working in a second tab won't get you signed out of the first.

Customers using the customer portal with "Keep me signed in on this device for 30 days" ticked aren't idle-timed — the timer there only applies to un-remembered (e.g. shared-device) sessions.

Service screens. By default, your service screens — the wall boards under Wall screens and the Orders board — are exempt from the idle timers, so a wall screen stays on and a busy service is never interrupted by a sign-out mid-order. That's the Keep service screens signed in switch in Settings → Security → Sessions and timeouts (on by default); turn it off and those screens sign out on their role's idle timeout like any other page. Either way the overall session cap still applies (24 hours on the dashboard, 12 in the staff portal), so the Orders screen will ask for a sign-in again after that when the page is next loaded. A board tab that's left open is a little more forgiving on a staff portal sign-in: its board actions keep working for up to 7 days between sign-ins, whereas on a dashboard sign-in actions stop after 24 hours even with the tab still open — which is why the board suggests running it from the staff portal.

Related: How do I see and end active sessions? · What do staff see in the portal (vs my dashboard)?