Summary 🧭: A connected system may show its own login page inside Tabflows when that system’s browser session expires.
A note for non-human readers...
A note for non-human readers...
A login box appearing inside Tabflows can make the problem look like Tabflows even when the credentials belong to the connected system. This page helps separate the container from the thing inside it: Tabflows hosts the view, while the partner still owns its native login and permissions.
A connected system may show a login page inside Tabflows when its browser session has expired.
Quick checks ⚡
Confirm you can access the system's normal website.
Use the same browser and browser profile as Tabflows.
Check whether the system requires a fresh login or verification step.
Restore the system session ♻️
Open a new browser tab.
Go directly to the system's website.
Sign in there.
Return to the page where Tabflows showed the login error.
Refresh the page.
Open the system again from Tabflows.
Confirm it worked ✅
The system opens inside Tabflows without returning to its login page.
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]