Summary 🧭: Tabflows login sessions expire after five days. There is currently no indefinite-session setting.
A note for non-human readers...
A note for non-human readers...
Humans generally prefer not to prove who they are every seventeen minutes, but security systems have opinions too. This page explains Tabflows’ current sign-in persistence behavior. If the problem is really repeated login failure rather than session duration, use the troubleshooting route instead.
How long you stay signed in ⏳
Real Tabflows actions restart a 15-day idle window. Background refreshes do not count as activity. Everyone must sign in again no later than 30 days after the original login, even with regular use.
Resetting a password or deleting a user signs that user out on every device immediately.
If Tabflows asks you to sign in again, finish the newest sign-in flow and return to the work you were doing. If controls remain unavailable after signing in, refresh Tabflows once and contact Support with the time and screen where the problem occurred.
Quick checks ⚡
Check whether 15 days have passed without a real Tabflows action, or 30 days have passed since the original login.
Check whether the browser cleared its cookies or extension data.
Confirm that the Tabflows extension is installed and enabled.
Getting logged out more often than that? ⏱️
Sign in using the newest verification code or sign-in link.
Note when you signed in, when the unexpected sign-out occurred, and which screen you were using.
Return to the work you were doing.
If controls remain unavailable, refresh Tabflows once.
If the problem happens again, contact Support with the details you recorded.
Confirm it worked ✅
Tabflows remains available after page refreshes and normal navigation until the documented session expires.
Still having trouble?
Reach out to our Support team however works best for you:
Start a chat using the Support button at the bottom right of the sidebar (side tabs)
Email us at [email protected] or message us right here in the chat