All posts
Guides
·
·
4 min read
Sessions, explained without the jargon
Tokens, refresh, revocation and multi-tab sync, in plain language for the rest of the team.

Ines Moreau
Co-founder and CEO

Sessions come up in every product meeting eventually. Someone asks why a user was signed out, or how long people stay signed in, and the answer is full of words like JWT and refresh token. Here’s the same answer in plain language.
Two keys, one short and one long
When someone signs in, they get two things: a short-lived pass that proves who they are for about a minute, and a long-lived key that can quietly fetch a new pass. Your app only ever checks the short pass, so it can do that quickly without asking our servers every time.
Signing out everywhere
Because the short pass expires so quickly, revoking the long key signs someone out of every device within a minute. That’s what happens when a user clicks “Revoke session”, or when an admin removes them from an organization.
Why tabs stay in sync
Open the app in three tabs and sign out in one. The others notice within a second, because they share the same long key and listen for changes. Nobody ends up half signed in.
Keep reading.
More from the blog.

Product
·
Passkeys are ready. Here's how we turned them on by default
What we learned switching passkeys on for 9,000 products, and the fallbacks that kept sign-in working for everyone else.

Tobias Lindqvist

Security
·
Why your sign-in page should never say “wrong password”
Small copy decisions that stop account enumeration without making the page harder to use.

Kwame Asante

Guides
·
A practical guide to organizations and roles
How to model teams, invitations and permissions so your B2B plan doesn't need a rewrite in a year.

Aarav Mehta